Scribd
Upload
55 views

Impetus: It Services Private Limited

JDK 1.4 introduced assertions to validate program assumptions. Assertions check that conditions are true and throw an error if not. They document assumptions and avoid performance penalties of if-else checks in production. Assertions should validate internal states but not public method preconditions, which should throw exceptions. Assertions enable detecting bugs and enhancing maintainability.

Uploaded by

hrishipisal
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
55 views

Impetus: It Services Private Limited

JDK 1.4 introduced assertions to validate program assumptions. Assertions check that conditions are true and throw an error if not. They document assumptions and avoid performance penalties of if-else checks in production. Assertions should validate internal states but not public method preconditions, which should throw exceptions. Assertions enable detecting bugs and enhancing maintainability.

Uploaded by

hrishipisal
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

impetus IT SERVICES PRIVATE LIMITED

Assertion (Since JDK 1.4)


JDK 1.4 introduced a new keyword called assert, to support the so-called assertion feature. Assertion
enables you to test your assumptions about your program logic (such as pre-conditions, post-
conditions, and invariants). Each assertion contains a boolean expression that you believe will be true
when the program executes. If it is not true, the JVM will throw an AssertionError. This error signals
you that you have an invalid assumption that needs to be fixed. Assertion is much better than using if-
else statements, as it serves as proper documentation on your assumptions, and it does not carry
performance liability in the production environment (to be discussed later).
The assert statement has two forms:
assert booleanExpr;
assert booleanExpr : errorMessageExpr;

When the runtime execute the assertion, it first evaluates the booleanExpr. If the value is true, nothing
happens. If it is false, the runtime throws an AssertionError, using the no-argument constructor (in
the first form) or errorMessageExpr as the argument to the constructor (in the second form). If an
object is passed as the errorMessageExpr, the object's toString() will be called to obtain the
message string.

Assertion is useful in detecting bugs. It also serves to document the inner workings of you program
(e.g., pre-conditions and post-conditions) and enhances the maintainability.

One good candidate for assertion is the switch-case statement where the programmer believes that one
of the cases will be selected, and the default-case is not plausible. For example,

1public class AssertionSwitchTest {


2 public static void main(String[] args) {
3 char operator = '%'; // assumed either '+', '-', '*', '/' only
4 int operand1 = 5, operand2 = 6, result = 0;
5 switch (operator) {
6 case '+': result = operand1 + operand2; break;
7 case '-': result = operand1 - operand2; break;
8 case '*': result = operand1 * operand2; break;
9 case '/': result = operand1 / operand2; break;
10 default: assert false : "Unknown operator: " + operator; // not plausible here
11 }
12 System.out.println(operand1 + " " + operator + " " + operand2 + " = " + result);
13 }
14}

Assertion, by default, are disabled to ensure that they are not a performance liability in the production
environment. To enable assertion, use the runtime command-line option enableassertions (or ea).
In the above example, "assert false" always triggers an AssertionError. However, the output is
different, depending on whether assertion is enabled or disabled.
> javac AssertionSwitchTest.java // no option needed to compile
> java -ea AssertionSwitchTest // enable assertion

impetus IT Services Pvt.Ltd.


B-16, First floor, Sant Tukaram Vyapar Sankul, Sector - 24, Nigdi, Pune, Maharashtra. India. Pin 411044.
Mobile 9970600774, 9730012775|Board 91-20-27640406|Fax 91-20-27641703
Email : [email protected] | Website : www.impetusits.in
impetus IT SERVICES PRIVATE LIMITED
Exception in thread "main" java.lang.AssertionError: %
at AssertionSwitchTest.main(AssertionSwitchTest.java:11)

> java AssertionSwitchTest // assertion disable by default

5 % 6 = 0

In the above example, since the "assert false" always triggers an AssertionError, you could choose
to throw an AssertionError. "throw" is always enabled during runtime.

default: throw new AssertionError("Unknown operator: " + operator);

Another usage of assertion is to assert "internal invariants". In other words, to assert the possible values
of an internal variable. For example,

1public class AssertionTest {


2 public static void main(String[] args) {
3 int number = -5; // assumed number is not negative
4 // This assert also serve as documentation
5 assert (number >= 0) : "number is negative: " + number;
6 // do something
7 System.out.println("The number is " + number);
8 }
9}

> java -ea AssertionSwitchTest // enable assertion

Exception in thread "main" java.lang.AssertionError: -5


at AssertionTest.main(AssertionTest.java:5)

Assertion can be used for verifying:


Internal Invariants: Assert that a value is within a certain constraint, e.g., assert x > 0.
Class Invariants: Assert that an object's state is within a constraint. What must be true about each
instance of a class before or after the execution of a method? Class invariants are typically verified
via private boolean method, e.g., an isValid() method to check if a Circle object has a positive
radius.
Control-Flow Invariants: Assert that a certain location will not be reached. For example,
the default clause of a switch-case statement.
Pre-conditions of methods: What must be true when a method is invoked? Typically expressed in
terms of the method's arguments or the states of its objects.
Post-conditions of methods: What must be true after a method completes successfully?

impetus IT Services Pvt.Ltd.


B-16, First floor, Sant Tukaram Vyapar Sankul, Sector - 24, Nigdi, Pune, Maharashtra. India. Pin 411044.
Mobile 9970600774, 9730012775|Board 91-20-27640406|Fax 91-20-27641703
Email : [email protected] | Website : www.impetusits.in
impetus IT SERVICES PRIVATE LIMITED
Pre-conditions of public methods
Assertion should not be used to check the validity of the arguments (pre-condition) passed into "public"
method. It is because public methods are exposed and anyone could call this method with an invalid
argument. Instead, use a if statement to check the argument and throw
an IllegalArgumentException otherwise. On the other hand, private methods are under your sole
control and it is appropriate to assert the pre-conditions. For example,
// Constructor of Time class
public Time(int hour, int minute, int second) {
if(hour < 0 || hour > 23 || minute < 0 || minute > 59 || second < 0 || second > 59)
{
throw new IllegalArgumentException();
}
this.hour = hour;
this.minute = minute;
this.second = second;
}

impetus IT Services Pvt.Ltd.


B-16, First floor, Sant Tukaram Vyapar Sankul, Sector - 24, Nigdi, Pune, Maharashtra. India. Pin 411044.
Mobile 9970600774, 9730012775|Board 91-20-27640406|Fax 91-20-27641703
Email : [email protected] | Website : www.impetusits.in

You might also like