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

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


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. 


Several methods exist to either prevent or mitigate this occurrence. 

Prevent Checked Out Test Cases From Being Executed:

The Test Execution Policy can be updated to prevent the execution of any test case that is currently checked out by a user. Add the following code to the Test Rules section for formal executions:
  1. {
                            "Is Allowed""No",
                            "Description""Checked Out Test Cases cannot be executed.",
                            "Constraints": [
                                    "Type""Field Is One Of",
                                    "Name""Version Status",
                                    "Values": ["Checked_Out"]

Mark Accidental Dry Runs as Draft Run = N When the Test Set is Ready for Execution

An action can be added to the transition dry runs to the Draft state and to update the Draft Run field to N when the Test Set is Ready for Execution. This code can be provided by Support.

WARNING: Editing policy files without a full understanding of the impact can cause errors or unwanted results. Edits should only be made by someone who has a complete understanding of their current configuration. If needed please feel free to reach out to Tx3 Support for assistance for this or any configuration changes you are planning.
    • Related Articles

    • 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 ...
    • Apache Log4j2 Remote Code Execution (RCE) Vulnerability - CVE-2021-44228

      Note — We will update this announcement with new details as they emerge from our analysis. Please check back periodically. Important: Security Vulnerability CVE-2021-44228 The Log4j team has been made aware of a security vulnerability, ...
    • 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.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, ...
    • 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 ...