public interface Check
NotNull check to the ith index of a sequence to
signify that the value returned by the statement at index i should not be null.
When a unit test is run as a regression test, it should have the same behavior as it did previously, and the Check objects represent that previous, expected behavior. Some examples of Checks are:
ExpectedExceptionCheck -- an exception should be thrown
NoExceptionCheck -- no exception should be thrown
ObjectCheck -- a particular ObjectContract should hold
Check objects. A Check object is
inserted as a decoration on a specific index of an ExecutableSequence. Thus, a check is
always associated with a specific index in a sequence. A check at index i means that the check is
to be performed after statement i finishes executing.
A check implements two methods that specify the code to be emitted before and/or after a
statement in a Sequence is executed.
A check may require some code to be emitted before and/or after the statement is printed. For
example, a check for checking that x is not null after the statement "Foo x =
m()" is executed might emit the assertion code "assertNotNull(x); ", and would do so
after the statement is printed. As a second example, a check for checking that an expected
exception is thrown by a statement would need to emit something like "try {" before
the statement, and the catch clause after the statement.
| Modifier and Type | Method and Description |
|---|---|
java.lang.String |
toCodeStringPostStatement()
Returns a string of Java source code to be emitted after a statement containing this check.
|
java.lang.String |
toCodeStringPreStatement()
Returns a string of Java source code to be emitted before a statement containing this check.
|
java.lang.String toCodeStringPreStatement()
java.lang.String toCodeStringPostStatement()