Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
sequencers [2021/02/17 18:08] admin [Sequencer - Priority Path] |
sequencers [2021/02/17 18:16] (current) admin [Sequencer - MCase] |
||
|---|---|---|---|
| Line 72: | Line 72: | ||
| Often times you may want to only test certain part of the model. | Often times you may want to only test certain part of the model. | ||
| - | //Mark Optimal// sequencer generates the test cases using the same [https://en.wikipedia.org/ | + | //Mark Optimal// sequencer generates the test cases using the same //Postman Problem |
| //Mark Optimal// sequencer (and [[# | //Mark Optimal// sequencer (and [[# | ||
| Line 90: | Line 90: | ||
| =====Sequencer - MCase===== | =====Sequencer - MCase===== | ||
| - | //MCase// is a collection of transitions that represents a custom test case. //MCase// sequencer generates the actual test sequence (test steps) to navigate through the model to cover the transitions included in the //MCase//. | + | //MCase// is a collection of transitions that represents a custom test case. //MCase// sequencer generates the actual test sequence (test steps) to navigate through the model to cover the transitions included in the // |
| The main use of //MCase// sequencer is to generate custom test cases, which can be used to test a bug fix, regression testing of important workflows and smoke testing. | The main use of //MCase// sequencer is to generate custom test cases, which can be used to test a bug fix, regression testing of important workflows and smoke testing. | ||