Create manual tests

Manual tests (including Gherkin tests) are generally used for acceptance testing. The tester tries most features in the application under test to make sure the application works as expected.

When creating manual tests, you can copy text from an external editor when creating scripts for a manual test. ALM Octane also provides version control capabilities for keeping track of manual test steps and Gherkin test scenarios.

Add tests

  1. Click + from the Tests tab in the Backlog or Quality module.

  2. Give the test a name, and select the Manual Test subtype.

  3. Assign test attributes. Make sure to enter values for the following attributes:

    Test type The type of test, such as acceptance, end-to-end, regression, sanity, security, and performance. You can assign multiple test types to a single test.
    Covered content This lets you check if you have requirement coverage. Select the items the test will cover. You can assign multiple backlog items to a single test.
    Application modules When you ready to use the test for tracking overall product quality, assign application modules to the test. You can assign multiple application modules to a single test. For details, see Work with application modules.
  4. Click Add & Edit.

  5. In the Steps tab, add the required test steps. For details, see Add test steps.

  6. In the Details tab, assign additional attributes, as required.

    Tip: Not sure you entered valid values? Do you think some mandatory fields do not have values? Click Show invalid fields and ALM Octane highlights only what needs to be fixed. Then click to see all fields again.

  7. Use these features to further maximize your productivity in ALM Octane:

    Select an image to learn more.

  8. Save the test.

After you assign the test to an owner, this test is included in a user's My Work list.

Team members can only delete items that they have created.

Back to top

Add test steps

After creating a manual test and specifying its basic attributes, add steps.

You can add the following types of steps to manual tests: 

Step type Description
Validation steps

Add a validation step when you want the tester to be able to specify a pass or fail status when running the test.

Validation steps are marked in the Visual Editor with an check mark icon:

Example:  

  • Step Login passes if the user successfully logged in.

  • Step Reserved fails if the user could not book a plane reservation because the plane was full.

Setup steps

Add a setup step when the tester has to perform an action, without indicating if the action passed or failed.

Setup steps are marked in the Visual Editor with a document icon: 

Example:  

  • Step Reboot instructs tester to reboot the system. No pass / fail status.

  • Step Calculate Tax figures out the amount of tax owed. No pass / fail status.

Call steps

Add a call step to have the current manual test call another manual test.

When the calling manual test runs, the steps of the called test are incorporated into the current run. When running the calling test, there is no indication that your test is running steps from another test.

Call steps are marked with a call icon in the Visual Editor:

Example:  

Step ConvertToDollars is used by many tests. It instructs the tester to perform the actions necessary to convert a currency amount into dollars. No pass / fail status.

  1. In the Steps tab of the test, in the upper right hand corner of the test steps pane, Select an editor, click the Visual Editor button or the Text Editor button .

  2. Add steps.

    Using the Visual editor

    Click Add Validation Step, Add Setup Set, or Add Call Step.

    • When adding a validation or setup step, describe the step in the text box that displays.

    • When adding a call step, a list of existing tests is displayed. Click the tests to call and then Select. You cannot add a description to the step.

    Using the Text editor

    Enter text directly in the Text editor. For the syntax, see Manual test syntax.

    Tip: You can create steps in the visual editor, and then switch to the text editor, to learn step syntax.

  3. View the steps of a called test:

    • Click the hyperlink of its ID to edit the called test's details.

    • Click to the left of the call step to view the called test's details. Click X to close the details.

  4. Save your test.

    Tip: While you work, you can save and label versions of your manual test. As you design your test, you can compare versions to view what has been modified, and by whom. For details about creating and working with versions of your manual tests, see Save and compare versions of test scripts.

Back to top

Next steps: