Model-Based Testing (using project models)

Slide 13 of 15

Model-Based Testing (using project models)

"Using the same project models as the developers do".
Making test specific models is a costly business and specialist designers/test engineers are needed to make it work. So be sure to pinpoint these heavy coverage and tooling only on the high risk areas.
On the other hand, when the ambition of Model Based Testing is lowered to only generating the test cases, it is a complete different story. Especially the generation of the (more global) logical test cases can be done from the same (functional and/or requirement) models the developers use as a bases for creating the software. For instance process flows (activity diagrams), decision tables and pseudo code are a perfect basis for generating (logical) test cases.
+ auto design of tests
+ systematic coverage
+ measure coverage of model and requirements
+ abstract tests
- automatic execution
- auto regression testing
See also COVER overview