A red line indicates a selected DataBlock

A red line indicates a selected DataBlock

Testing in the context of the MxSuite involves creating Stimulus Patterns and Response Patterns. A pattern is a shape describing how a Signal changes over time. These patterns can be defined by Transition Lists or Signal Generators. We call these patterns DataBlocks.  This abstraction is a useful building block as we create a syntax for constructing a comprehensive test environment. Some attributes of DataBlocks:

By default a Signal has one DataBlock.

Within a TestCase, and for a particular Signal, you can string several DataBlock patterns one after another.

A DataBlock has a Duration, and if you create DataBlocks, they need to be named so that they can be referenced.

The last DataBlock for a Signal extends indefinitely to the right.

DataBlocks for Response Signals can each have their own Pass/Fail criteria.

You can define Variant patterns for a DataBlock.

Use Cases for DataBlocks

So a DataBlock defines a block of behavior.  Here are some practical applications of DataBlocks:

You can define that you don't care how a Signal changes in a certain time range by creating a "Don't Care" DataBlock.

Each DataBlock can have its own source of data (Transition List or Signal Generator).  Concatenating DataBlocks allows you to construct more complex patterns.

You can define TestCases with different Pass/Fail tolerances at different times in the test.

You can define pass/fail criteria based on the relative time between two DataBlocks.  The DataBlocks may be defined for the same Signals or for different Signals.

You can have Signals in several TestCases refer to the same DataBlock pattern (stored in an external data file).  This offers a significant reuse potential.

You can use Variant DataBlocks to test patterns with minor differences. You can specify any variant passes, or only the active variant.

Related Topics:

Data Block Overview

Transitions

Variant DataBlocks