Tests

Overview

The categories of service assurance tests are:

• ping tests (subclasses of sas.Ping)

• trace tests (subclasses of sas.Trace)

• actions (subclasses of sas.Action)

The types of each test are:

• test (subclass of sas.Test)

• deployed test (subclass of sas.DeployedTest)

• test definition (subclass of sas.TestDefinition)

Generally, deployed tests are transient objects that are created when the sas.Test is run. The deployed test is removed after the test is completed. The results are retrieved from the NE and associated with the sas.Test.

Note: The NFM-P supports OmniSwitch ping and traceroute tests via user-defined CLI scripts instead of sas package objects. For sample scripts, see the sample OmniSwitch ping and traceroute CLI scripts in the NSP NFM-P Classic Management User Guide. For information about deploying CLI scripts, see CLI command methods .

To create a test using the OSS interface, use generic.GenericObject.configureChildInstance. The CreateServiceTunnelPing.xml file in the code samples demonstrates the creation of a svt.TunnelPing test with default values. See the XML API Reference for the test class and additional test properties. See the XML API SDK Sample Code Navigator for sample XML code.

To run an existing test, use the executeAndWait method of sas.Test. See the XML API Reference for method parameters. Several sample usages are available in the XML API code samples; for example, LspPing-UserExisting.xml. See the XML API SDK Sample Code Navigator for sample XML code.

The sas.Test object provides a convenience method to create and run a test using an XML request. See sas.Test.adhocExecuteAndWait in the XML API Reference for more information. Several sample usages are also in the XML code samples; for example, LspPing-CreateAndUse.xml. See the XML API SDK Sample Code Navigator for sample XML code.

See “OAM diagnostic tests” in the NSP NFM-P Classic Management User Guide for a list of the OAM diagnostic tests that are supported by the NFM-P. Classes for most tests are in the packages for the tested elements; for example, ATM ping is defined in the atm package. The only exception to this is Ethernet CFM tests, which can be found in the ethernetoam package. See Packages for information about mapping entity types to packages.