When it comes to executing tests, there are two important things to bear in mind when working with Jubula :
![]() |
The well-defined state of your AUT may be completely empty, or may contain test data. Deciding what data your test needs and what data it will create itself is an important part of an automation strategy. |
Use cases are then grouped together into Test Suites . The Jubula team uses the following Test Suites in their tests:
The FULLTEST Test Suite contains all of the executable Use Cases from the Project . There can also be Test Cases which reproduce errors from the bug-tracking system, called ticket tests. Each ticket Test Case can be linked to the bug-tracking system via its ID.
The FULLTEST_BROKEN Test Suite contains any use cases which are currently broken and which have been removed from the FULLTEST so as not to affect any test reports or statistics. Put tests in the broken Test Suite if they have been broken for some time. Tests that are critical, or which should be fixed in the next build, should be left in the FULLTEST Test Suite .
The WORK Test Suites can be used by testers as a sandbox to execute single use cases during specification, or to replay tests with the intention of watching the execution.