Manual testing flow

This flow demonstrates how to create and run manual tests for measuring release and product quality. For full details, see the relevant topics.

Select an image to learn more.

Overview

For manual testing, ALM Octane supports 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. 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.
  • Defects. You can report defects while running manual or Gherkin tests.

Back to top

Create tests

You can create tests in the Quality module and in the Backlog module, or inside a Story.

  • 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.
  1. From the Tests tab in the Backlog module, the Quality module, or inside a Story, click + to create the test.

  2. Name the test, and in the Subtype field, specify if it is a manual test, a Gherkin test, or a test suite.

  3. To track release quality, specify Covered content.

  4. To track product quality, specify Application modules.

  5. Enter other attributes as necessary. Click Add & Edit to add steps or scenarios.

  6. Add manual steps or Gherkin scenarios.

    For details on adding manual steps, see Add test steps. For details on adding Gherkin scenarios, see Add test scenarios.

    As you add steps and scenarios, you can save versions of your tests. For details, see Save and compare 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 Use rules to customize how you work.

For details on creating manual tests, see Create manual tests. For details on creating Gherkin tests, see Create Gherkin tests.

Back to top

Create test suites

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.

Back to top

Run tests

Run tests with the Manual Runner.

  1. Choose the test and press Alt+R to launch the Manual Runner.

  2. When starting a run, you can specify: 

    • The release to associate with the run.

    • Details about the environment on which you are running the test.

    • Whether this is only a draft run. The results of a draft run are not tracked.

  3. In the Manual Runner, enter actual values for each step or scenario as you perform each step in the application under test.

  4. Assign each step or scenario a status: Passed, Failed, Not completed, Blocked.

  5. Report defects as necessary by clicking .

  6. Click to end the run.

Note: For details on running manual tests, see Run manual and Gherkin tests.

Back to top

Report defects

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.

  1. Press Alt+N to create the defect.

  2. Name the defect, and assign a Severity.

  3. To track release quality, specify Covered content.

  4. To track product quality, specify Application modules.

  5. Click Add & Edit to continue assigning other attributes to this defect. For example, in which environments did you find this defect? 

Note: For details on creating defects, see Report and track product defects.

Back to top

Analyze results

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.

  1. To analyze overall quality, use the Dashboard module.

  2. To analyze the quality of the backlog or application modules, navigate to the Backlog or Quality module and click Overview.

  3. Examine the relevant widgets. For example:

    Tests by phase A chart that shows you how many tests are in each phase, such as New, In Design, and so on.
    Weekly status - New tests by designer A chart that shows you how many tests have been created this week by each designer.
  4. 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.

  5. 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.

Back to top