MCase View allows you to create mCase to describe certain scenarios. MCase is a collection of transitions and it can be executed by mCase sequencers. The order of the transitions in mCase may or may not be significant depending on which mCase sequencer is used.

With MCase View, you can create and edit mCase and the member transitions. To open MCase View, right mouse click on the model canvas and select “MCase View” from the context menu.

To create a new mCase, click on “Add mCase” button in the header area of MCase View. Add transitions to an existing mCase by right click on transitions, click on “Add to MCase” memu item and select an mCase from the mCase dropdown list. Transitions added to mCase become mCase steps, which can be deleted or moved up or down via context menu action.

By default all MCases are enabled and will be executed in order one at a time by any MCase sequencer. You may disable any MCase that you wish not to be executed by clicking on U icon next to the MCase, which will toggle MCase execution flag on (enabled) / off (disabled).

Similarly you may disable / enable steps within an MCase by clicking on T next to the MCase step.

You may highlight all of the transitions in an mCase by clicking on the MCase label.

You can move MCase View by dragging it on the header section. MCase View can also be resized by its sides or the lower right corner resizer. Vertical and horizontal scrollbars will only be displayed when needed.

The alternative to mCase is to mark transitions in the model and select “Mark” option on the IDE side bar. When you execute the model, TestOptimal will automatically generate test steps to cover all marked transitions.