Create manual tests

Create manual tests in ALM Octane.

Create tests and add test steps

When you are ready to create manual tests, create the test entity and the steps in the same process.

To create manual tests:

  1. In the Backlog or Quality modules, or the Tests tab of a test suite, click + and select Manual Test.

  2. In the Add Manual Test dialog, 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.
    Backlog coverage The backlog items the test will cover. This helps you track the release quality.
    Application modules The product's application modules. This helps you track product quality, regardless of release.
  3. Click Add & Edit.

  4. In the Steps tab of the test, click the Visual Editor button or the Text Editor button .

  5. Add the required test steps:

    Validation steps

    Steps that check something in the application. During the test run, you specify a pass or fail status for each validation step.

    ALM Octane displays validation steps in the Visual Editor with an check mark icon:

    Setup steps

    An action in the application. During the test run, you do not need to state if the step passed or failed.

    ALM Octane displays setup steps in the Visual Editor with a document icon: 

    Call steps

    Call and run the steps of another manual test.

    ALM Octane displays call steps with a call icon in the Visual Editor.

    Note: If you add steps in the text editor, there is a specific syntax to use to ensure you add the correct steps. For details, see Manual test syntax.

  6. (Optional:) Add attachments. In the toolbar, click Attach to add files and navigate to the desired file or paste an image directly into the test.

    ALM Octane adds the attachment as a separate step in the test. Also, view the file in the Attachments tab of the test, the Manual Runner when starting a test run, or the test run report.

  7. Save your test.

    Tip: While you work, save and label versions of your manual test. As you work with the test over time, compare versions to view modifications. For details, see Use versions of test scripts.

Back to top

Use parameters in tests

You can create tables with parameters and parameter values for re-use in manual tests. When you run a test, it runs in multiple iterations using a different set of parameter values each time.

Here's a simple example showing a list of users and passwords. Each iteration will use a different set of values:

To work with parameters: 

  1. When creating a test that will use parameters, click the Parameters Table button.

  2. In the pane that opens on the right, either create a new table, or choose a saved table from the dropdown options.

  3. Enter a name for the table, and click on each column header to rename the column. Each column represents a parameter.

    Parameter names cannot contain empty spaces or angle brackets (< >).

  4. In each row, enter a set of parameter values.

  5. To add or remove rows or columns, click the dropdown arrow next to the row or column name. The arrow is visible when you hover over a cell or column header.

  6. Click Save when your table is ready.

  7. You can use the menu options next to the Save button to manage your parameter tables. If you select Remove from test, you disconnect the table from the current test but it is still saved in ALM Octane. If you select Delete table, it is removed from all tests that are using this parameter table. ALM Octane shows you which tests use the table before you delete it.

  8. In the relevant test step, enter parameter names using the following syntax: <parameter name>.

    Tip: You can also quickly access the list of parameters by pressing CTRL-SPACE. Use the keyboard arrows to navigate the list, and Enter to select a parameter.

  9. When you run the test, it runs in multiple iterations. Each iteration uses a different set of parameter values from the table.

    Using the above example, here are the results of a run:

Back to top

Next steps: