Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
mcase [2020/05/10 16:10] admin removed |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== MCase ===== | ||
| - | |||
| - | //MCase// is an a collection of states and transitions of the model to represent a specific test scenario or a set of scenarios. | ||
| - | |||
| - | ---- | ||
| - | ==== MCase Sequencers==== | ||
| - | //MCase//s are executed by these two sequencers: [[sequence_mode# | ||
| - | |||
| - | The states and transitions do not need to be consecutive. // | ||
| - | |||
| - | ---- | ||
| - | ==== MCase Use Cases ==== | ||
| - | //MCase// allows you to perform incremental testing of parts of your application affected by the changes. You can create as many //MCase// as you need and execute subsets or all of //MCase// at will. | ||
| - | |||
| - | You can also create Data-Driven testing using //MCase//. As each transition in an //MCase// is traversed, a specific row from the test dataset can be retrievedto set up the test scenario. | ||
| - | |||