Formal Approval and Closure of Test Runs

As part of You must login to see this link. Register now, if you have no user account yet. a new test management workflow was released and all existing Test run trackers were migrated to. The new workflow adds support for formal, audit-ready test executions.

Brief Overview of the New Workflow

The new workflow extends the previous ones with a few additional statuses and transitions that formal test runs rely on, while making all previous statuses more meaningful as well. This includes the following improvements:

• All regular workflows now go to a "Ready for execution" state when created
• In case of formal workflows, the test run gets created in a "To be approved" state, which can be approved to be "Ready for execution" or "Rejected" to support formal acceptance before executing a Test run
  • Rejected test runs cannot be executed and are considered Closed
• There is also a new "Closed" state after a Test run is "Finished" to support formal closures after Test run execution
• The "To be approved" and the "Finished" statuses can both have a "Start a new review" action for "On Entry" to benefit from workflow based reviews
• A new "Formality" field was introduced to keep track of the type of the test run -- they can either be "Regular" or "Formal"
• The coloring of the various states have also been made more distinct for easier recognition

Configuring the Approval and Closure Workflow

In order to benefit the most from the new To be approved and Closed states, you may want to configuring workflow based reviews on them. To do so, you need to click on the "To be approved" and/or "Finished" statuses respectively and tailor the review configuration to your needs as described at: Start a new review

Using Formal Test Runs

Formal test runs can be created by generating a new test run from a test case or test set, and selecting "Create as formal Test Run" at the "Create Test Run as formal or as regular?" option.

By doing so, the test run will be created being in the "To be approved" status. These test runs cannot be run until it is approved either through regular workflow transitions or based on review results (depending on the tracker configuration).

Once they are approved, formal test runs can be run the same way as regular ones.

After test execution, finished test runs (both regular and formal) can optionally be closed. This additional state transition can be used to represent an acceptance or approval on the test results. This action can also be done by a simple state transition or based on review results (depending on the configuration of the test run tracker).

Migration of Existing Test Run Trackers

See the related documentation at: Test Management Workflow Migration