Run manual and Gherkin tests

Run tests within ALM Octane using the Manual Runner.

How ALM Octane runs tests

Depending on the type of test, the Manual Runner runs tests differently:

  • When running a manual test, view the test steps and add details on the steps. For each validation step, assign a run status. After the test run, ALM Octane creates a compiled status .

  • When running a Gherkin test, view scenarios. For each scenario, assign a run status and assign one for the test.

Note: The run statuses you assign when running manual tests (including Gherkin tests and test suites) are called native statuses. When analyzing test run results in the Dashboard or Overview tabs, ALM Octane categorizes the native statuses into the summary statuses Passed, Failed, Requires attention, Skipped, and Planned for clarity of analysis.

Back to top

Run tests

Run manual tests or Gherkin tests from ALM Octane.

Tip: You can also run manual tests using Sprinter, as described in Run and edit manual tests in Sprinter.

To run tests:

  1. In the Backlog or in the Quality module, select the tests to run.

  2. In the toolbar, click Run .

    The Run tests dialog box opens, indicating how many tests you are about to run. Specify the test run details:

    Run name

    A name for the manual run entity created when running a test.

    By default, the run name is the test name. Provide a different name if necessary.

    Release and environment

    The product release version to which to associate the test run results and the application environment on which you run the test.

    By default, ALM Octane uses the last selected environments.

    Script version

    Select Use a version from another release to run a test using a script version from a different release. If there is more than one version from the selected release, ALM Octane uses the latest version.

    Any tests linked to a manual test from a Add Call Step use the same specified version.

    Draft run status

    Select Draft run if you are still designing the test but want to run existing steps. After the run is complete, ALM Octane ignores the results.

  3. Click Let's Run! to run the tests.

    The Manual Runner opens.

    Tip: During the test run, click the Run Details button to add run details.

  4. Perform the steps as described in the step or scenario.

Back to top

Assign statuses to test steps

Ensure that you record the status of the test as you perform test steps or scenarios. This enables ALM Octane to use the results in quality analysis.

To assign statuses to test steps:

  1. If necessary, click the check mark next to the step or scenario.

  2. In each step or scenario, record your results in the What actually happened? field:

Back to top

Report defects during a run

If you encounter problems when running a test, open defects or link existing defects.

To open defects during a test run:

  1. In the Manual Runner toolbar, click the Test Defects button .

    If you want to associate the defect with a specific step, next to the step, click the Add Defect button .

  2. In the Add run step defect dialog box, fill in the relevant details for the defect and click Add.

    The new defect form is automatically populated with the application module of the test where the run originated, as well as the release that was chosen to run the test. Other relevant fields are filled as well.

  3. To link the run to an existing defect, click Link to defect, select the relevant defect(s), and click Select.

  4. Click to view a list of the defects for this run.

  5. To copy test run steps to the defect's Description field, click Copy steps to description. This helps you reproduce the problem when handling the defect.

    • In a manual test, if the defect is connected to a run, all the run's steps are copied. If the defect is connected to a run step, the steps preceding the failed step are copied. If there are parameters in the test, only the relevant iteration is copied.

    • In a Gherkin test, the relevant scenario is copied.

Back to top

Add attachments to a run or step

It is sometimes useful to attach documentation to the run.

To attach items to a run or a step in a run:

  1. Do one of the following, based on where you need to attach information:

    • To attach to a test run: In the toolbar, click the Run Attachments button .

    • To attach to single step: In the step, next to the What actually happened field, hover and click the Add attachments button:

    In the dialog, attach the necessary files.

    Tip: Drag and drop from a folder or paste an image into the Manual Runner.

ALM Octane updates the Manual Runner to show the number of attached files:

Back to top

Stop the run and see results

View the results after a complete test run to see the status and details.

To view the results:

After performing all steps, at the bottom of the ALM Octane Manual Runner window, click .

Note: If you have not marked all steps or validation steps, the run status is still listed as In Progress. Finish entering and updating step details to change the status.

In the Runs tab of the test, click the link for your specific manual run and view the results in the Report tab.

The report displays step-by-step results, including the result of all validation steps, and any attachments included in the run. You can also see which phase the test was in when the run was created.

Tip: To view test phase information for multiple runs, add the Test Phase column to the Runs tab.

Back to top

See also: