mCase is an executable group of states and transitions which are to be executed together to test certain scenarios. mCase are executed by mCaseSequencer. When run with multiple virtual users, you are exposing your application to a more realistic simulation of production use pattern.

You can place any states and transitions in an mCase. The states and transitions need not be consecutive. TestOptimal has a built-in optimization algorithm which will find the shortest test sequence to traverse (test) all states and the transitions in mCase with minimum duplicates. This is a well-known Chinese Postman Problem.

mCase allows you to perform incremental testing or testing parts of your application affected by the changes. And you can create as many mCases as you need and execute subset or all of mCases.

You can also create the Data-Driven-Test automation using mCase and dataset. First place all transitions to be tested in an mCase, then define and populate dataset from your backend database or Excel Spreadsheet in mCase setup script, and finally retrieve one row of data from dataset (to set field value on the screen or verify the results) each time mCase is executed. A very simple and easy way to develop a Data-Driven-Test automation.