The SUT is the entity that you are testing. In the MxSuite environment, the SUT may be a model, compiled C/C++ code, electronic test equipment, or an MxTransIt Virtual Wiring Harness. Some common things about SUTs, whatever their form:
•All SUTs have input (stimulus) and output (response) Signals.
•For a useful test, all stimulus and response Signals should be evaluated as a set. Usually, it is not meaningful to evaluate an isolated stimulus and response pair without considering the transitions of other Signals in the system.
•The Signals in the MxVDev TestCases need to be connected to the I/O of the SUT. Sometimes there is a simple one-to-one mapping between the Signals, and often some kind of transformation needs to be performed on the Signal (such as offset, scaling, or filtering).
•The SUT and MxVDev are connected using the Virtual Wiring Harness (or Harness for short).
•A SUT should be designed so that it can be set to a known state. Once it is initialized to that state, it can be ticked and its response tested. When a project is loaded, a connection is automatically established between MxVDev and the SUT.
•You can set up a test environment with one or more SUTs.