# Dry Running Test Scripts (Validation Management)

Validation Management allows test script authors to request that users dry run a specific test script to verify its accuracy prior to submission for pre-approval and test script execution. From the user interface, assigned dry run executors can provide comments on the test script and its test steps, identifying scripting errors or suggesting improvements. Upon completion of the dry run, test script authors are prompted to review comments, resolve or reject feedback, and make adjustments to the test script as part of the authoring process.

The Test Dry Run Interface is not available by default and requires an Admin to configure the _Test Script_ object to accommodate the execution of dry runs.

## About the Test Dry Run Interface {#test-dry-run-interface}

When you perform the **Start Dry Run** action on a test that is in the _In Authoring_ or _Dry Run Authoring Review_ lifecycle states, the Test Dry Run Interface becomes available to the assigned Executor.

### Test Header

This section includes the _Test Script ID_ if available or the _Name_ with the _Title_ of the test script being authored. If the test name and title are too long to display, you can hover over the header to view the full name and title.

### Navigation Panel

The navigation panel on the left side of the interface allows you to select either the Step View or Comments View. This panel, along with the comment panel, adjusts automatically based on screen resolution and browser window size to optimize users' interactions with the panel. You can collapse the panel by clicking (<i class="far fa-chevron-double-left"></i>) and expand it by clicking (<i class="far fa-chevron-double-right"></i>).

#### Step View

Similar to the Test Authoring Interface, this view displays sections, setup steps, and execution steps of the test script. Click on a step or section in this panel to navigate directly to it in the content panel. You can collapse and expand sections to efficiently navigate through large numbers of test steps.

#### Comments View

This view displays comments captured during the dry run. From this view, you can add a comment for the _Test Script_ or select a specific test step in the content panel to add a comment. Once a comment is saved, it is stored in the Comments View, and you can click the comment to select and expand it to see more details. 

Click the ellipses at the top of a saved comment to **Edit**, **View Details**, or **Delete**.

Click the ellipses at the top of the Comments View to **Expand All** or **Collapse All** comments.

Click the filter icon to filter the comments by their status. Click **Apply** to set the filter options, or **Reset** to remove them.

### Content Panel

Similar to the Test Script Execution Interface, the content panel in the lower right portion of the interface contains the _Setup Steps_ and _Execution Steps_ which you will dry run. The content panel displays up to 25 steps per page.

To add a comment for a specific test step, select the test step in the content panel and populate the comment from the Comments View.

### Status & Action Bar

The top right of the interface includes a next step locator icon <i class="fal fa-crosshairs"></i> which takes you to the next incomplete step in the _Test Script_.

### Taskbar

The taskbar displays under the test header and lists the Executor's assigned task, the associated task instructions, and the task due date. The task due date color changes based on the number of days remaining until the task is due. A green due date means that five (5) or more days are remaining, an orange date means that less than five (5) days are remaining, and a red date means that the task is overdue.

The taskbar also displays a _Show More_ or _Show Less_ link and a _Complete_ button. Click the **Show More** link to expand the taskbar to display the full instructions for the task. Click the **Show Less** link to collapse and hide the instructions. The _Complete_ button allows the Executor to complete their assigned task. If configured by an Admin, Executors are prompted to provide a verdict and eSignature once they click **Complete**.

## Performing a Dry Run

To dry run a test step as the assigned executor:

  1. Navigate to a _Test Script_ record in the _In Dry Run_ lifecycle state.
  2. From the Test Dry Run Interface, <a href="/en/gr/50533905/#execute-test-steps">execute test steps</a> in any order, providing attachments and verdicts as needed. Vault does not require you to complete all test steps in order to complete the dry run.
  3. [Add comments][1] where necessary.
  4. Click **Complete** to finish the dry run.

The _Test Script_ transitions to the _Dry Run Complete_ state, where the author can [review the comments from the dry run(s)][2]. The lifecycle state of all comments transitions from _Draft_ to _Submitted_.

### Adding Comments {#adding-comments}

To add comments during a dry run:

  1. From the Comments View, select a **Type** from the drop-down. Alternatively, select a specific test step from the content panel to create a comment for that step.
  2. Optional: If you are creating a comment for a test step, select a **Step** from the drop-down of existing test steps. If you select a test step from the content panel, Vault automatically populates this field.
  3. Optional: If applicable, select a **Prompt**.
  4. Select a **Category** to provide context for the comment. For example, _Scripting Error_.
  5. In the text box, provide a comment.
  6. Optional: Select the upload icon to provide an attachment for the comment.
  7. Click **Save**.

## Reviewing a Dry Run {#review-dry-run}

When the assigned executor completes a dry run, the dry run _Test Script_ enters the _Dry Run Complete_ state. Vault displays read-only comments in the Test Authoring Interface from the dry run(s). The source _Test Script_ may be in the _In Authoring_ or _Dry Run Authoring Review_ state. From the source _Test Script_, the author can review all saved comments in the Comments View and **Mark as Resolved** or **Mark as Rejected** using the provided buttons. Authors and Executors also can filter comments in the Comments View by lifecycle state. From the content panel, edit each test step's title, prompts, settings, or requirements as needed and according to the dry run comments.

Click **Complete** to complete your authoring and review or click **Start Dry Run** to execute another dry run for this test script. Once the dry run review is complete, the _Test Script_ can proceed to pre-approval, and the dry run is captured in a section on the source _Test Script_ record.

## Related Permissions

To use the Test Dry Run Interface, users require a security profile and a permission set which grants these minimum object and field-level permissions:

  * _Validation Test Script Comment_: Read, Create, Edit, Delete
  * All fields on the _Validation Test Script Comment_ object: Read
  * _Test Script_: Read
  * _Test Script Dry Run?_ and _Source Test Script for Dry Run_ fields on the _Test Script_ object: Read
  * _Source Test Script for Dry Run Steps_ and _Source Test Step for Dry Run_ fields on the _Test Step_ object: Read
  * _Source Prompt for Dry Run_ field on the _Additional Prompt_ object: Read


  [1]: #adding-comments
  [2]: #review-dry-run