Experience has shown that it is more effective to iterate between working on the model and test generation instead of investing a lot of time into model change and “see what happens” when you click test generation button on the entire model after days of modelling. Chances are that, especially in more complex models (see section MODEL COMPLEXITY Model Complexity), there are basic modelling construction issues that either prevent test generation to achieve a 100% coverage or unnecessarily increase test generation time. Remember to generate tests from subactivity diagrams instead of only the complete model to speed up and simplify analysis (see section Generate Tests Often and Keep 100% Coverage).
Recommendation: Generate tests frequently after completing (partial) changes to your model, e.g., one of your many activity diagrams, to ensure that changes do not trigger unintentional or unexpected behavior and work with the rest of your model. Verify the steps of the partial flow, even if the tests do not make sense in the overall model context. |
...