Editing test runs
Edit a test run to enter test results or change the information in it.
Tip: If you need to update field values for multiple test runs, use bulk change fields to quickly update multiple items simultaneously. See Bulk changing fields to update multiple items.
1. In the Test Runs list, click next to the test run and choose Edit. You can also click the number or summary and then click Edit on the Viewing Test Run page.
The Edit
Note: Icons
2. Make any changes to the custom fields and test variant information in the overview area.
3. Make any changes to information on the tabs in the
Tab | Displays: | More information |
---|---|---|
Steps | Steps to perform the test, expected results, and actual results. | Running tests
|
Files | Files attached to the test run, including scripts for automated tests and files attached from source control applications, such as Surround SCM. | Viewing and downloading file attachments |
Workflow | Work performed on the test run as it moves through the workflow. | Viewing workflow event history |
Email sent about the test run. You can reply to email. Available only if email tracking is enabled for the project. | Viewing email and Replying to email | |
Traceability | Items linked to the test run and options to perform impact analysis. You can add, edit, and delete links, mark linked items as suspect to indicate they may be impacted by changes, and investigate suspect dependencies. | Working with item links and Performing impact analysis |
Folders | Folders the test run is included in. You can add the test run to other folders, move it to different folders, or remove it from folders. You cannot add or move the test run to public folders you do not have permission to modify or are locked, or locked private folders. You cannot remove the test run from locked folders. | Organizing items with folders |
Baselines | Baselines the test run is in. You can view the test run as it was when added to the baseline, view differences between the current test run and test run in the baseline, and view differences between the test run in two baselines. | Working with baselines from items |
History | Historical information about the test run, such as when it was created, when it was last modified, and all actions performed on it. | Viewing item history |
4. Click Watch to be notified every time the test run changes. See Watching items to be notified about changes.
5. Perform any additional actions.
- To move the test run through the workflow, click a workflow event button. For example, click Assign to assign it to another team member. Click More to see additional events. See Adding workflow events to items.
- To perform various actions on the test run, click Actions and choose an action.
- To run a report that includes information about the test run, click and choose a report. See Running reports.
- To send email about the test run, click and choose an option. See Emailing from Helix ALM.
6. Save the test run.
- Click Save to save and close the test run.
- Click Apply to save and continue working on the test run.
Tip: If the changes impact linked or related items, you may want to mark the items as suspect. This flags the items to indicate they should be reviewed. See Marking items as suspect.