Test Execution

Create test instance by adding tests to test suites, schedule and run test instances. Analyze test runs and link issues.

Create Test Suites

As your application under tests changes, you run the tests to detect issues. In order to execute tests you create test suites. You can choose the tests to add to each test suite. Test suites can be organized in a hierarchical tree structure. You can assign a release cycle to a testsuite folder, therefore all test suites and their test instances will be automatically assigned to this release cycle.

Add Tests and Requirements

You can choose the tests to add to each test suite. This can be done directly by adding the tests or indirectly by selecting requirements. When you select a requirement all tests covering the requirement will be added to the test suite. Once you add a test to a test suite it will further be called test instance.

Add Test Configurations

Once you added a test or requirement to a test suite you can select the test configuration to be used for test execution. The test instances of a test suite are orded. You can reorder the execution flow. You can add the same test with same or different test configuration multiple times to a test suite.

Schedule Test Instances

You can control the execution order of test instances (tests) in a test suite. You can also schedule the date and time for executing a test and select the responsible user to execute a test. You can create custom fields and custom relationships e.g. to link the test environment for test execution.

Run Test Instances

When you run a test instance (test) manually, you follow the designed test steps and perform actions on your application and compare the expected results

with the actual outcome. You can execute a test instance as many times as needed - each execution is a test run. If you execute a test instance multiple times in the same target release, the result of the lastest execution will be associated with the test instance. All test runs are linked to the test instance.

Link Issues

Issues (Defects) can be directly linked to test runs, test instances, test suites, tests, requirements, releases and cycles. Indirect links will be automatically created. E.g. if you link a defect to a test instance, a indirect link will be created for the test, the covered requirements, the test suite, the release cycle and release. This is essential for requirement to defect traceability.