Test suites

Overview

Test suites are used to group OAM tests. After the suites are created, they can be scheduled to provide periodic results or run on demand to investigate service issues. Test in a suite are organized in the following groups:

• first-run tests

• generated tests

• last-run tests

First-run tests typically include high-level diagnostics, such as service-side or VPRN ping. The tests can be run sequentially or in parallel. Generated tests are run after the first-run tests. See Generated tests for more information about generated tests. Last-run tests typically include transport-layer diagnostics, such as an LSP trace or a tunnel ping, and can also be run sequentially or in parallel.

Test suites are usually associated with a specific type of tested entity, such as VLL service or VPLS. You can also create a test suite with a mix of tested entities by setting testedEntityType to none (1).

To create a test suite, use the generic.GenericObject.configureChildInstanceWithResult method to create a child of the sas object. For a simple example, see CreateSimpleTestSuite.xml. See the XML API SDK Sample Code Navigator for sample XML code.

To add tests to a test suite, use sas.TestSuite.addTest or addTests. To run a test suite, use the sas.AbstractTest.execute method. For an example, see ExecuteTestsFromTestSuite.xml. See the XML API SDK Sample Code Navigator for sample XML code.

See “Service Test Manager” in the NSP NFM-P Classic Management User Guide for more information about test suites. See the XML API Reference for more information about the properties and methods of sas.TestSuite.