Entering manual test results in text view

Manual test runs displayed in text view include steps and expected results as text. Markup codes indicate the type of text line.

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. Select the manual test run on the Manual Test Runs list window and click Edit.

The Edit Manual Test Run dialog box opens.

2. Click the Steps tab.

The read-only test case steps are displayed.

3. Perform each step in the manual test run. Make sure the actual results match any expected results provided.

Markup codes indicate the type of text in each line, such as steps and expected results. See Test case and manual test run markup codes.

Attachments may be included in the steps to provide additional information you need to perform the test. Click an attachment link to view it.

4. If an issue occurs when you perform a step, enter a Problem Statement to describe the problem.

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

5. Click Go To Test Case to view the related test case. See Viewing test cases.

6. Click Create Issue to add an issue to report any problems found during testing. See Creating issues from manual test runs.

7. Click Send Email to email a user about the manual test run. See Emailing from Helix ALM.

8. Save the manual test run.

  • Click OK 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.