Draft Runs

Setting a test as a draft run instructs ALM to ignore the run results. When you set a test instance as a draft run, the outcome of the run does not impact the execution status of the test, the status of the test instance, or the coverage status. ALM also ignores draft runs when calculating the remaining number of test instances to run, and when displaying results in coverage, progress, and live analysis graphs.

You can designate a test run as a draft before you perform the test. You can also mark a test run as a draft by modifying the Draft Run field at any time after the run. When you change the Draft Run value for a run, ALM recalculates all relevant statistics, and updates relevant status fields. Graphs display updated results.

Draft runs enable you to try tests while they are still in development, or after they have been modified. For example, you may want to test that each step description is formulated correctly, or try only a part of a large test script.

Setting a test run as a draft requires the appropriate user permissions. For details, see Manage user groups and permissions.

For task details, see Work with draft runs.

Parent topic: Test Execution Overview