Executing Test Cases


Execution Overview

Executing a test case is term used to describe the process of performing the steps in a test case and logging the result, such as whether it worked properly (passed) or had errors (failed).


Starting Execution

To start execution, click the execute icon, pictured above, and select the environment that results should be stored against. If no environments have been created, execution will not be permitted.


Stopping Execution

To stop and execution and return to editing mode, simply click the stop icon.


Saving Execution Results

To save any changes in the result, notes or reference number fields, the save button must be clicked.


Setting a result for Test Cases

When the tester has finished performing the steps outlined in the test case, he or should should record the results of the test. Select from one of the following results, check the item in the list and click the save button. Optionally, you may add a reference number and notes.


Adding Notes

Notes should be added for every result recorded, indicating, for example what data was used to run the test or the specific error that was returned for a failure.


Adding a Reference Number

This field was designed to record the ticket number for the associated bug that was filed as as a result of a failure.


Viewing or Adding Attachments

Attachments can be viewed and added to while executing tests. Click on the paperclip icon at the top right corner of the form.


Viewing Execution History

Each time a test case is executed, the results are recorded as a separate entry, including any notes and the reference number. To view this history, click the book icon at the top right corner of the form. The most recent result is shown in the center of the form, using the color defined under Preferences. By default, for example, a failed test would be indicated by the color red.


Navigating Through a Series of Test Cases

After saving the result the current test case, you can use the arrow icons to move to the next item in the list. The tree can also be used for navigating through test cases as usual.


See also

Setting filters.