Defines a sequence of tests that can be run in the specified order with several execution settings.
All test types can be mixed. Although, UI mobile tests will be executed always at the end of the execution now.
It is possible to add a parameterless procedure as a setup object and also as a teardown object, i.e. the setup procedure will be executed before the first test in the suite and the teardown procedure will be executed at the end of the suite execution, regardless of the test results.
There are two ways for adding test objects to a test suite.
- Typing in a test name in a test line
- Dragging and dropping tests inside the test lines part
There are some properties that can be set for a Test Suite object
- Continue On Error: it indicates whether the next suite must be executed or not if this suite fails. Default: true
- Retries: number of times to retry the suite if it fails. Default: 0
- Set Up Object Name: procedure without parameters to be executed before the tests of the suite. For example, a procedure that creates some registers in DB needed for test execution.
- Tear Down Object Name: procedure without parameters to be executed after the tests of the suite. This procedure is always executed regardless of intermediate test results.
Every test you add to a suite can be configured with some extra settings:
- Continue on error: it indicates whether the next test must be executed or not if this test fails. Default: true
- Retries: number of times to retry the test if it fails. Default: 0
- Iterations: it is a visual shortcut if you want to execute N times an item and, instead of having N lines with the same test and the same configuration for each one, you can have a single line with iterations = N.
You can run a suite by right-clicking on it and selecting the option Run Suite or from the Tests Explorer window similar to running tests.
Suites can also be run from MSBuild tasks in your CI pipeline.
This object is available since GeneXus 17 upgrade 3.