Teledyne LeCroy SierraNet M408 User Manual Ver.1.50 - Manual (Page 213)

SierraNet M408 Protocol Analyzer User Manual 211
InFusion Scenarios Teledyne LeCroy
Note: You can specify additional Sequences and States. The application automatically checks for the
maximum number of terms (sequences/states). When you exceed the limit, an error is flagged,
prompting you to jump to the place that caused the error.
Creating InFusion Scenarios is easy, but it requires an understanding of the following
terms defined in Table 4.3.
TABLE 4.3: Key Scenario Terms
4.5.4 Scenario Actions
After you enter the set of Events for a test state, the menu‐driven interface prompts you
for the corresponding Action or set of Actions. If you define multiple Actions, the Actions
occur simultaneously.
Note: The Actions displayed are dependent on the Events selected.
Term Definition
Action InFusion response to an Event. See “Scenario Actions” on
page 211 .
Event Condition that is detectable by InFusion. See “Scenario Events” on
page 201 .
Combined Event Logical OR association of Events (for example, Event A OR Event
B).
Global Rules Portion of a Scenario that can define a single InFusion test state.
You can think of the Global Rules and each Sequence as a
separate test routine or program operating within the Scenario.
Each operates independently and in parallel with the others. The
purpose of each is to detect Events and then respond with the
appropriate Action or set of Actions. In essence, you can operate
up to three test states simultaneously within InFusion ‐ one is the
Global Rules, and the other two are the 2 active states, one in
each Sequence. See
“Global Rules” on page 221 .
Sequence Portion of a Scenario that can define multiple InFusion test states.
More flexible than the Global Rules, a Sequence allows more
powerful Scenarios that include branching and looping between
test states (Global Rules can define only a single test state, so
there is no branching). See
“Sequences” on page 222 .
State “Behavior” of the Global Rules or a Sequence at any point in time.
In terms of InFusion testing, behavior is “waiting” for a set of
Events and responding with a set of Actions.