Concepts and Terminology

•Project - This is an environment that stores all the configuration information needed to specify, develop and test the system.

•Real Time/Accelerated Time - This Project Setting determines the type of clock used for your test.

•Signal - An input or output of the system (can be numeric, message, event, or task).

•Signal Dictionary - A repository for information about all the input and output signals for the system.

•Transitions - A single change in a single Signal is a transition.  A Transition is specified in terms of Signal Name, Time, and Value.

•Signal Pattern - A Signal pattern is the definition of how a Signal changes over time during the execution of a Test.

•Viewing Signals - Signal patterns are color-coded to indicate if they are commanded, expected, or actual patterns.

•Signal Classifications - Signals are classified as numeric, message, or event.

•Signal and Port Properties - Signals and ports have properties that are defined in MxTransit and the Signal Dictionary.

•DataBlock - A DataBlock is a sequence of changes to a Signal. A sequence is defined by an ordered set of Transitions, by a standard equation, or by a custom code snippet.

•Null Data - Null data means the Signal has no value at the given time. It is not the same as a value of zero.

•TestCase - A TestCase is an executable element that groups together Input Signals and Output Signals.  It may have Input Signal Profiles to stimulate the System.  It may also have Output Signal Profiles.  These output profiles represent either the expected behavior of the System or the Actual behavior of the System.

•Scenario - A Scenario provides a way of building more complex test scenarios from a sequence of one or more simpler TestCases.  It allows you to schedule TestCases to run in sequence or concurrently.

•Regression Test - In the MxSuite, a Regression Test is a set of Scenarios. You can select all available tests or focus on a subset of interest. One advantage of a Regression Test is that it produces a comprehensive report of the test and its results.

•Reactive and Parameterized Tests - Reactive tests enable you to define test requirements with C# code. With parameterized tests, you can run use the same TestCases and Scenarios to run tests with variable requirements.

•Triggers - A Trigger 'fires' when a predefined circumstance occurs. It can occur when a Signal changes or exceeds a Threshold. Triggers are defined in the context of a DataBlock.

•Min/Max Ranges - The min/max range provides another level of pass/fail checking.

•Tolerances - Tolerances define how close the comparison must be for the test to be considered a pass. There are tolerances for transition times and values.

•System Under Test (SUT) - The SUT may be hardware (HIL), software (SIL), or a model (MIL).

•Virtual Wiring Harness (also called the Harness or Test Harness) - MxSuite offers a way of creating test suites that is independent of the form of the System Under Test.  The Virtual Wiring Harness provides a way of connecting the test to the SUTs.  It also enables you to perform transformations on the signal data as it streams between the SUT and MxVDev. Use MxTransit to create and modify the Harness.

•Transforms - Transforms are used to form the Virtual Wiring Harness and connect to the SUT.

•System Signals - System Signals control and monitor the operation of MxVDev and the Test Harness. System Signals are predefined and always available. You can add them to your tests just as you would add other Signals. System Resets are an example of a System Signal.

•System Reset - A key philosophy of the MxSuite is that unless you explicitly reset the test system (SUT and MxSuite) the system remains in the state it was in upon completion of any prior test or Scenario. This is exactly the same behavior as you would see when testing a real piece of hardware in a bench test environment. You can use System Signals to perform resets when desired. For a description of the behavior of the reset Signals, see System Reset.

•Constants and Calibration Sets - A Constant is a value defined before a test is run. A calibration set is a set of values that can be assigned to a Constant.

•Tags and Tag Groups - Tags can be used to control Regression Tests, Constants, Variant DataBlocks, and Reactive code.

•Tick Period - Transforms have a tick period which controls how often they read their inports and transmit from their outports.

•Code Snippet - A piece of C# code defined within the MxSuite environment.  It is used to define a Signal Profile, or to perform transformation on a Signal.

•Virtual Buses - The MxSuite provides virtual CAN and LIN buses, which can be connected to real hardware buses.