This flow demonstrates how to create and run manual tests for measuring release and product quality. For full details, see the relevant topics.
When testing using ALM Octane, you can use any of the following
|Manual tests||Manual tests are the most basic and efficient way to start tracking quality. Manual tests contain a list of actions that the user might perform when using the application.|
Gherkin tests are also manual tests. Gherkin tests are written in a natural language syntax which makes them very readable. You might want to create a Gherkin test for parameterization, or as a step towards automation. Gherkin tests provide a structure which helps facilitate a line-by-line automation approach, if you choose to automate your tests.
Both manual and Gherkin tests are saved as text files, and can be edited either inside or outside of ALM Octane. ALM Octane also has built-in version-tracking capabilities for manual steps and Gherkin scenarios.
|Test suites||You can define a series of tests in a test suite, and run the test suite. This facilitates reuse.|
You can report defects while running manual or Gherkin tests.
You can create tests in the Quality module and in the Backlog module, or inside a story.
In the Tests tab in the Backlog or Quality modules, or the Tests tab inside a story, click + and select the type of test to add. Then provide the test or test suite details.
The test is then assigned accordingly:
In the Quality module, tests you create are associated with the application module selected in the Application Module tree.
In the Backlog module, tests you create are associated with the feature selected in the backlog tree or with the story in which you create the test.
You can also associate tests with the Backlog later, by specifying backlog items in a test's Covered content field. Similarly, you can always update a test's Application modules field to associate a test with an application module.
As you add steps and scenarios, you can save versions of your tests. For details, see Use versions of test scripts.
Example: You can create a rule that a version must be approved, or signed off, before moving it into production. This could be useful if you need to achieve FDA compliance or meet certain security requirements. For details on rules, see Set up rules for workflow.
Consider grouping tests into test suites. Tests can be called from multiple test suites. This allows you to reuse tests. For full details, see Create test suites.
Run tests with the Manual Runner.
Choose the test and press Alt+R to launch the Manual Runner.
In the Manual Runner, enter actual values for each step or scenario as you perform each step in the application under test.
Assign each step or scenario a status: Passed, Failed, Not completed, Blocked.
Report defects as necessary by clicking .
Click to end the run.
Note: For details on running manual tests, see Run manual and Gherkin tests.
While designing and running your tests, you can report defects.
Create defects from the Defects module, or the Defects tab of the Backlog or Quality module.
You can also create defects while running a manual or Gherkin test with the Manual Runner by clicking during the run. Press ALT + N to create the defect and then enter the defect's details
For details on creating defects, see Report and track product defects.
ALM Octane comes with many useful graphs for analyzing release and product quality. You can customize the predefined widgets ALM Octane provides or design your own by configuring custom widgets.
To analyze overall quality, use the Dashboard module.
To analyze the quality of the backlog or application modules, navigate to the Backlog or Quality module and click Overview.
Examine the relevant widgets. For example:
Tests by Metaphase A chart that shows you how many tests are in each phase, such as New, In Design, and so on. Feature quality status A chart that shows you how many test runs have been carried out each feature.
Filter the information that the charts include, by using the panel on the right. For details on filtering, see Filter items.
You can also set filters as part of a widget’s configuration. These settings remain the same each time you view the dashboard.
Example: Filter by environment tags to view statistics for specific environments only.
To add more widgets to the dashboard, click +. Select from the available widgets or create new ones.
For details on analyzing quality, see Use the ALM Octane Dashboard.