Working with an Active Test Run

The following applies to Modules, Test Cases and Test Steps.

When a Test Run is activated, the user can navigate to any Module, Test Case or Test Step to enter Test Results. When navigating to a Module, the child Test Cases in the Test Case list will be displayed differently depending on certain factors:

1. Child is a leaf: The Test Case will have input fields for Comment and Action, as well as buttons to set the Test Result (the default results are Pass, Fail, Skip and Block). Action can be None, Create Bug, or, if a bug already exists for this Test Case, Update Bug. Choosing New Bug or Update Bug will take the user to New Bug or Edit Bug in FIT | BugTrack, and return them to the TestSpec module afterwards.
2. Child is a leaf, but already has a result: the result, result date, user and comment will be shown for the Test Case. Also, an Edit link will appear that will allow the user to edit the result and comment.
3. Child is not a leaf: a summary of the Test Case's children's results will be shown (default # Pass / # Fail / # Tests).

There is also an Update Selected section to enter many results at once.

Screenshot showing an active Test Run: Creating a bug for a failure during the execution of a Test Case

Screenshot showing an active Test Run: Entering the bug information for the failed Test Case

Screenshot showing an active Test Run: After bug is entered, user is returned to their place in the Test Run