Test Set - Dry Runs

Test Set - Dry Runs

What are Dry Runs? 

Test Set Designers can designate a Test Set for Dry Runs. Dry Run Test Sets will ONLY produce informal executions (Dry Run executions). Once a Test Set is put into Dry Run Status, there is no way to reverse the action.

Dry Run Test Sets are useful for running a preliminary suite of tests for unproven processes or features that are likely to result in failed Runs. In a standard VERA configuration, Dry Run Test Sets are easily deleted by using the Smart Delete action. When the Test Set is deleted, the Dry Run executions are removed along with it, helping to keep the project’s Test Runs list tidy.


Steps to Create a Dry Run Test Set

1.      Select a Test Set which is in Draft Status. The Test Set may not contain any formal runs.

2.      Open the VERA Action Menu.

3.      Click the “Test Set(s) Dry Runs” Action


4.     Ensure that the correct Test Set(s) are selected in the dialog box.

5.      The Test Set’s Status becomes Dry Run


What are the limitations of using Dry Runs?

Dry Run Tests Sets will only produce Dry Run executions which do not affect the Execution Status of a Test Set and does not require approvals will not contain signatures. 

Marking a Test Set as Dry Run is an action that cannot be reversed, and any runs that are produced cannot be recognized as formal executions. 

**** If formal executions are needed, a user may execute the Smart Copy action on the Test Set and then use Smart Paste to duplicate the Test Set. This will create an exact copy of the Test Set except that it will have a Status of Draft and any execution data will have been excluded. ****

    • Related Articles

    • How to Prevent or Fix Dry Runs created in Ready for Execution Test Set

      Problem: Rarely, dry runs (i.e. runs with the Draft Run field set to Y) can be created in formal test sets. This is due to an ALM feature that automatically marks runs created from a "Checked Out" test case as Draft Run = Y.  Prevention/Mitigation: ...
    • Receive following error when submitting runs for approval: Index was out of range. Must be non-negative and less than the size of the collection, Parameter name: index

      If you receive this error please check the "Testers" (Not "Tester") and confirm: 1) That the "Testers" field is not populated 2) Username in "Testers" field is no longer assigned to the project. If either one of these cases is true (Testers field is ...
    • Gaps in ALM Run ID sequence

      Problem Runs appear to be deleted in a VERA configured ALM project.  Here are known ways that runs appear to be deleted: A user opens a test in ALM.  When a run is started, the Run is created in the database.  If at any time, including if the user ...
    • VERA for ALM 2.1 released!

      Today, we are very pleased to announce the latest version of VERA. This VERA 2.1 release includes support for ALM 12.55 patch 1, the ability to add custom actions and toolbar buttons, improvements to the Test Set Approval process and improvements to ...
    • VERA for ALM 2.7 released!

      Today, we are very pleased to announce the latest version of VERA for ALM. The following improvements were made: Customer’s VERA configuration can be updated to allow Test Administrators to correct Test Runs that failed to copy the values of GxP, ...