Entering manual test results in grid view

Manual test runs displayed in grid view include test steps, expected results, and attachments organized in rows and columns.

If issues occur during the test, you can enter problem statements to indicate how the actual results are different from expected results. Problem statements, which are used when creating issues from manual test runs, should be specific so other users can reproduce the issue. For example, if you perform a step to log in to the tested application and the login fails, you can enter the error displayed or other behavior that occurs.

Review all information in the manual test run before running the test and entering results. See Running manual tests.

1. In the Manual Test Runs list, click the gear icon next to the manual test run and choose Edit.

The Editing Manual Test Run page opens.

2. Click the Steps tab.

The read-only test case steps are displayed.

3. Perform each step. Make sure the actual results match any expected results provided.

The Attachments column may provide additional files you need to perform a step. Click an attachment to view or download it.

4. If an issue occurs when you perform a step, click the corresponding cell in the Problem Statement column and enter information to describe the problem.

You can also add attachments to help other users understand issues you encountered. See Attaching files.

5. Select the check box in the row when you complete the step. This can help you track your progress in the manual test run.

6. Click Actions and choose Add Related Issue to add an issue to report any problems found during testing. See Creating issues from manual test runs.

7. To email a user about the manual test run, click the Email button and choose an option. See Emailing from Helix ALM.

8. Save the manual test run.

  • Click Save to save and close the manual test run.
  • Click Apply to save and continue working on the manual test run.
If the manual test run is complete, make sure you enter the overall test result (e.g., Passed, Failed, or Undetermined). See Entering overall results for manual test runs.