Share this page

# Create test suites

A test suite is a collection of tests. Use test suites to test an area of your application, for regression testing events, and so forth.

A test suite can contain manual tests, Gherkin tests, and executable automated tests. For details, see Testing.

In this topic:

## Overview

A test suite is a collection of tests. Test suites do not contain any content of their own.

Use test suites in a variety of ways:

- Group tests of a particular page, module, or section of your application together. This lets you test that section of the application.

- Keep tests of a particular theme grouped together. You can reuse the same test suite across versions, and compare the suite run from the current version with those from previous versions. In addition, you can run the same suite on different environments and compare suite runs to check for any regressions.

- Different people run the tests. The owner of the test suite receives the compiled results for the test suite's test. This method is particularly helpful for regression testing.

## Create test suites

To use test suites, you must create the container of the test suite.

To create a test suite:

1. Open the Tests page in the Quality or Backlog modules.

2. If you want to add tests directly to the new test suite, select those tests in the grid.
3. Right-click in the tests grid, and select Create Test Suite.

4. Set the test suite attributes. In particular, we recommend you provide a value for the Backlog coverage and Application modules attributes.

Back to top

## Add tests to a test suite

You can add tests to a test suite either from within the test suite, or from the Tests page.

You can add the same test to a suite multiple times, so for example you could run an automated test twice using different environments or execution parameters.

To add tests to a test suite from within the test suite:

1. Open the Tests page in the Quality or Backlog module.
2. Open a test suite and select its Planning tab.

3. To add existing tests to the test suite:

   1. Click the Add Existing Tests button.
   2. Select all the tests you want to include.
   3. Click Add.

4. To add new tests to the test suite:

   1. Click the Add button and select whether to create a Manual Test or a Gherkin Test.
   2. Select all the tests you want to include.
   3. Specify values for the fields.
   4. Click Add. The new test that you created is automatically added to the test suite.

To add tests to a test suite from the Tests page:

1. Open the Tests page in the Quality or Backlog module.
2. Select the tests you want to add to a test suite.
3. Right-click, and select Add to Test Suite.
4. In the Add to Test Suite dialog box, select all the test suites to which you want to add the tests.

Back to top

## Parameterize UFT One tests

If you add executable UFT One tests to a test suite and your UFT One Git repository contains data tables, parameterize your test runs using data tables.

Tip: For ALM Octane to locate the data tables in Git, store them in an entirely separate folder from your tests.

To parameterize your test runs using data tables:

1. In the test suite, open the Tests tab and select the grid view.
2. Add the Data table column to the grid.
3. In the UFT One test's row, select a data table to use for the test run. The list of data tables includes all of the data tables that ALM Octane discovered with your tests.

When the suite runs this test, it will run with the data table you selected.

To run a test with different data tables, add the test to different test suites. In each suite, you can specify a different data table for this test.

Back to top

See also:

- Plan and run test suites
- Plan and run manual and Gherkin tests

https://admhelp.microfocus.com ALM Octane 8942
Tips to improve your search results... ValueEdge & ALM Octane Help Center ValueEdge ALM Octane Help 16.0.100-16.0.400 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: