In this lab, you will learn about assertions in Java. You will learn how to create assertions and when to use them. Assertions are used to test assumptions regarding our code and are mostly utilized during the testing phase of the software.
Let's create a simple assertion that tests if a number is even. We will assume that the number is even and write an assertion using an even number. We will then alter the number and run the code. We should get an AssertionError.
public class AssertionsLab {
public static void main(String[] args) {
int number = 4;
assert (number % 2) == 0;
System.out.println("Number is even");
// change the value of number variable to odd
number = 3;
assert (number % 2) == 0;
System.out.println("Number is even");
}
}By default, assertions are disabled in Java. We can enable assertions using command-line options.
Let's use the -ea option to enable assertions and run the code.
java -ea AssertionsLabThe code should print "Number is even" followed by an AssertionError.
Let's now disable assertions using the -da option and run the code again.
java -da AssertionsLabThe code should print "Number is even" twice without throwing any exceptions.
Assertions can also be used to test inputs to a method. Let's create a divide method that takes two parameters and returns the quotient after dividing the first parameter by the second parameter. We will assume that the second parameter is non-zero and create an assertion to check it.
public class AssertionsLab {
public static void main(String[] args) {
int a = 10;
int b = 5;
int result = divide(a, b);
System.out.println("Result: " + result);
// change the value of b to zero
b = 0;
result = divide(a, b);
System.out.println("Result: " + result);
}
private static int divide(int a, int b) {
assert b != 0 : "Cannot divide by zero";
return a / b;
}
}We can use assertions for debugging and testing. Assume that we have a program that reads a file and returns the first non-zero number from it. To test this program, let's create an input file with three numbers.
echo "0\n3\n0" > input.txtLet's write our program that reads the file and returns the first non-zero number from it. We will then create an assertion to test if the program returns the correct output.
import java.io.File;
import java.io.FileNotFoundException;
+ import java.util.Scanner;
public class AssertionsLab {
public static void main(String[] args) throws FileNotFoundException {
Scanner scanner = new Scanner(new File("input.txt"));
int number = 0;
while (scanner.hasNext()) {
number = scanner.nextInt();
if (number != 0) {
break;
}
}
assert number == 3 : "Incorrect number read from file";
System.out.println("First non-zero number: " + number);
}
}Assertions are not suitable for validating arguments of public methods. These assertions may be disabled during runtime which can lead to unexpected behavior.
public class AssertionsLab {
public static void main(String[] args) {
int negativeNumber = -1;
printPositiveNumber(negativeNumber);
}
public static void printPositiveNumber(int number) {
assert (number > 0) : "Not a valid positive number";
System.out.println("Positive number: " + number);
}
}We can add informational messages to assertions to make them more informative and provide better feedback in case of a failure. We will now modify the assertion in the previous code to include an informative message.
public class AssertionsLab {
public static void main(String[] args) {
int number = -1;
assert (number > 0) : "Negative number found";
System.out.println("Number is positive: " + number);
}
}The message "Negative number found" will be displayed when the code is executed.
The purpose of assertions is generally to find bugs when testing software. However, if the assertions themselves break code, then it becomes problematic. For example, a transient network error or a timing issue on a system can cause an assertion to fail. Additionally, if we use assertions to validate inputs on public methods, we run the risk of leaving our system unprotected against invalid and malicious inputs.
One way to circumvent the negative impact of assertions is to use them judiciously. Use assertions only for things that should never happen in a well-designed system.
public class AssertionsLab {
public static void main(String[] args) {
double result = squareRoot(4);
System.out.println("Square root: " + result);
double negativeNumber = -4;
result = squareRoot(negativeNumber);
System.out.println("Square root: " + result);
}
public static double squareRoot(double number) {
assert number >= 0 : "Number should be non-negative";
return Math.sqrt(number);
}
}It is important to avoid side effects while using assertions. We should avoid changing variables within assertions. Instead, the expressions should be used to detect problematic situations and provide more diagnostic information.
public class AssertionsLab {
public static void main(String[] args) {
int firstNumber = 1;
int secondNumber = 2;
assert (firstNumber = secondNumber) == 0 : "Values are not equal";
System.out.println("Values are equal");
}
}We can use assertions to check if all possible cases of a switch statement have been covered. Let's create a switch statement that returns the name of a day based on its number. We will assume that the number is within the range of 0 to 6 and create an assertion to check it.
public class AssertionsLab {
public static void main(String[] args) {
int dayNumber = 2;
String day = getDayName(dayNumber);
System.out.println("Day: " + day);
// set dayNumber to an invalid number
dayNumber = 10;
day = getDayName(dayNumber);
System.out.println("Day: " + day);
}
public static String getDayName(int dayNumber) {
String day;
switch (dayNumber) {
case 0:
day = "Sunday";
break;
case 1:
day = "Monday";
break;
case 2:
day = "Tuesday";
break;
case 3:
day = "Wednesday";
break;
case 4:
day = "Thursday";
break;
case 5:
day = "Friday";
break;
case 6:
day = "Saturday";
break;
default:
assert false : "Invalid day number";
}
return day;
}
}Congratulations! You have completed the Java Assertions lab. You can practice more labs in LabEx to improve your skills.
