We call scenario a test where all iterations are not doing the same thing.
For example, in a bank account management, you may need to execute different operations with different data inputs.
The simplest way to achieve this with Tmar is to use a column dedicated to define which operation has to be executed. Developers will be able to use this column value to find what to do with each iteration.
Tmar also allows having different headers for iterations in the same test description. That way different information may be provided or expected results given depending of the operation.
Dealing with scenario
Define, Share and Automate your tests / specifications