Run manual and Gherkin tests
You run manual tests, Gherkin tests, and test suites in ALM Octane's Manual Runner.
Depending on the type of tests you are running, the Manual Runner adapts to show relevant information.
When running a manual test, you see test steps. You can assign a run status to the overall test and also to its steps.
When running a Gherkin test, you see scenarios. You can assign a run status to the overall test and also to its scenarios.
When running multiple tests, you name the set of tests and you see each test run sequentially. You can assign a run status to the overall test and each test's steps/scenarios.
When running a test suite, you see each test in the suite run sequentially. You can assign a run status to the suite's test and each test's steps/scenarios.
In the Backlog or in the Quality module, select the tests to run.
In the toolbar, click Run Test .
The Run tests dialog box opens, indicating how many tests you are about to run. Specify the test run details:
By default when running a single test, the run name is the name of the test. Provide a different name if required.
If you are running multiple tests, provide a name.
Release and environment
Specify which product release version to use for the test run and the environment on which to run the test.
For convenience, the last environments you selected are automatically loaded when you run additional tests.
You can run a test or test suite using a script version from a different release than the one specified in the Release field. The Release field specifies the current release in which you are running the test.
To use a script version from a different release, select the Use a version from another release check box, and select the release of the script version that you want to use. If there is more than one script version related to the release you selected, the latest script version will be used.
When you run a manual test, any tests linked to it via the Add Call Step automatically run on the same specified version.
Draft run status
If you are still designing the test, you can run the test anyway, and have ALM Octane ignore the results. Check Draft run.
Click Let's Run! to run the tests.
The Manual Runner opens.
During the test run, you can also edit run details by clicking the Run Details button at the top of the Manual Runner window.
As you perform each step or scenario, click the check mark next to the step, scenario, test, or test suite to assign a status.
Status Description Passed Results were as expected. Failed Ended in an error or the results were not as expected. Not Completed The run was not completed. Blocked Run could not be executed, perhaps because of an external dependency.
For each step, you can record your results where its says, What actually happened?.
While running tests, you can create new defects or link existing defects to steps, scenarios, or the entire run:
In the Manual Runner toolbar or next to the step, Click the Add Defect button or the Test Defects button at the top of the Manual Runner dialog box.
In the Add run step defect dialog box, fill in the relevant details for the defect and click Add.
Note that when you open a defect from a step, many relevant fields are already filled in, such as the feature, application module, depending on where you opened the test.
To link the run to an existing defect, click Link to defect, select the relevant defect(s), and click Select.
The total number of defects opened for this run is indicated at the top with: .
Click to view a list of the defects for this run.
Click to stop the run when you are done.
In the Runs tab, view the results. The most recent run is listed first.
In the Tests tab, in grid view, look at the Test status column.
If you hover over the Test Status indicator, a legend appears. The legend explains how many tests were run, and what their status is.
Click View Runs from the legend to go directly to the runs of the test.
In the Runs tab for a test, in the Smart view, view the run status, the most relevant field.
In the Runs tab for a test, in grid view, view all details of the run status. For example, add the column Test version to see the script revision that was run. This is useful to trace back to the test to see what a particular script revision included.
In the Runs tab for a test or test suite, click the link of a run to drill down to further details. For example, click the Report tabs to view a run report.