assertions : Java Glossary

1. to check for expected error conditions.
2. to verify your code does not contain bugs.
3. to make sure when your program goes insane, you find out about it as soon as possible before it destroys all traces of what went wrong.

For (2) you use asserts which can be turned off once you are sure the code is solid.

For (3) you trust the run time array subscript out of bounds and null pointer checking.

Design by Contract

Bertrand Meyer in Eiffel pioneered the use of structured assertions in a system he called Programming By Contract. These serve both to document the preconditions (require) on parameters coming into a method, and the guaranteed characteristics of the result (ensure). Unfortunately, Java still does not support them. They can be crudely added with the JaWa preprocessor.

Java 1.4.1+ has a feature Sun calls assertions but they are so pathetic they don’t deserve the name. It is as though Sun wanted to claim that Java has assertions without doing any work to implement them and not caring if the final product was actually of any use. If Sun wants to try again, they should look at how Eiffel assertions work.

They are new language feature, not just a new class.

Enabling

In Eclipse, you enable assertions by using the JDK 1.5 level then click run ⇒ arguments ⇒ VM arguments then enter -ea. There is no checkbox to tick.

Coding

assert a > b : "a must be bigger than b";

To mark a place in your code you should never get, you can code an assertion that always fails like this:

assert false : "Fell out bottom of loop without finding elt.";

Learning More