Creating a New Test

Often the requirements are predefined. At a minimum, the requirements should specify the purpose of the system and the functions necessary to accomplish its purpose. It may be helpful to structure the tests to correspond to the structure of the requirements to verify that each requirement is met.

Define which parts of the system to include in the test. Is your test is a unit test or an integration test? Is your SUT hardware or software? It is often necessary or more convenient to use more than one test to test all parts of the system.

Harnessing is the process of connecting the SUT to MxTransIt. Harnessing requires one or more Transforms. The selection of the Transform and the method of harnessing depends on the type of SUT: software, model, hardware, or a combination.

MIL

SIL

HIL

After you have selected the Transforms, create a project in MxVDev, and then use MxTransIt to create the Transforms and harness the SUT. Set the Properties of your Transforms.

The input and output Signals available for interacting with your SUT are represented by ports on the Transforms in your Harness. For User-Defined Transforms, you may be able to add additional Signals. It is not necessary to use all available ports in your test. Use this procedure:

1.Set the port properties for the ports you are using.

2.Export the ports from MxTransIt to MxVDev.

3.Connect the Signals to load them into the MxVDev Signal Dictionary.

An MxVDev test has four levels of hierarchy:

1.Signal - must be included in a TestCase

2.TestCase - a collection of Signals

3.Scenario - a collection of TestCases

4.Regression Test - a collection of Scenarios

A simple requirement may be tested with a single TestCase; more complex requirements usually necessitate one or more Scenarios. Regression Tests are usually used to test the entire system. In general, best practice is to use a separate TestCase for each requirement or group of closely related requirements.

There are significant benefits to a modular test design:

•Easier to debug

•Easier to maintain

•Easier to isolate problems

•Easier to evaluate results and reports

•Avoids conflicts if a Signal is used differently for testing multiple requirements

•Reusability of modular test steps

The last step is to create the parts of your test in MxVDev:

1.Create the TestCases.

2.Specify the tolerances (time and value).

3.Specify the expected results. See:

•Accept Results

•Editing Test Patterns

•Manipulating Signals

4.Create the Scenarios.

5.Optionally, create a Regression Test.