Enforcing Test Evidence
- 1 Minute to read
- Print
- DarkLight
- PDF
Enforcing Test Evidence
- 1 Minute to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
You can enforce adding test evidence by testers, for Passed Steps / Planned Runs. Testers can add evidence during manual test execution (for Passed Steps).
Note
- You will need the Test Create / Edit / Delete / Mass Edit permission in order to change the Evidence Required field
- Users can generate / upload evidence if they are assigned with the Test Run Edit and Execute / Retest permission
- The default value for the Evidence required field is No.
To set the Evidence Required field to Yes for specific Test Steps or Planned Runs -
- Open up a Test / Quick Test and select the Steps / Planned Runs tab
- Use one of the following options -
- Option I - Highlight the relevant Step and click on View Step
In the General tab, scroll down to the Evidence required field and set it to Yes / No - Options II - Click on the Select Column button
Begin typing "evidence", or simply select the Evidence required field from the drop-down list by scrolling.
Now you can edit this field for each step, in the steps grid.
- Option I - Highlight the relevant Step and click on View Step
- Upon execution, the tester will be required to upload the Test Evidence
Good to Know!
You can also set the Evidence required field -
- When importing tests from file
- Using the Mass-Edit button in the Test Tree or List to edit the Evidence Required field for multiple Test Steps / Planned Runs