Executing Tests

Tests can be simple one-liners or extremely complex issues with a lot of detail, steps, links, and files associated with them. Nevertheless, once a test has been created, the next logical thing to do is execute it. Executing a test means providing a high level status on what happened when the test was run or "executed" and doing some follow-up actions on that (like filing a bug for example).

Test executions can happen in many ways. Based on how the testing process for your project is set up, you can be executing tests in one of the following ways:

  1. Create a test and execute it right away in an ad-hoc manner.

  2. Create a test cycle, create a test and execute it right away as part of that cycle.

  3. Create test cycles, create many tests and add them to various test cycles and then methodically execute from a cycle.

  4. Search for test executions and execute them from the resulting search result set, both in the List View and Detail View.

Combinations of the above are possible but it is important to pick a certain process and stick with it for the duration of the project or a version in order to gain efficiencies in the execution and test reporting process.

See Also

Ad-hoc Executions

Creating, Cloning and Viewing Test Cycles

Publication date: