|
You can now define your tests in the test model. This
model is organized as a testing hierarchy familiar to
JUnit users:
test: the top level test suite |
 |
test Suite 1 |
| |
 |
context1: test case 1 |
| |
|
 |
sequence diagram 1: test method 1 |
| |
|
|
sequence diagram 2: test method 2 |
| |
|
context1: test case 2 |
| |
|
|
sequence 1 diagram 1: test method |
| |
|
|
sequence diagram 2: test method 2 |
| |
|
|
... |
| |
test Suite 2 |
| |
... |
The main particularity is that tests methods are defined
in a UML sequence diagram. You can add as many test
methods as you wish to a context, as many contexts as
you wish to a test suite and as many test suites as
you wish to the top level test suite.
A test method is created with a sequence diagram. "Assert"
notes, which allow the specification of a test, can
be added to return messages. The code corresponding
to that test method is automatically generated and inserted
into a JUnit test case class.
|