Differences
This shows you the differences between two versions of the page.
Both sides previous revision
Previous revision
|
Next revision
Both sides next revision
|
tutorial:debugging [2020/07/19 16:15] admin [Debugging test generation] |
tutorial:debugging [2020/07/19 16:22] admin [Debugging test generation] |
As you may have picked up the error in the model - it breaks the first condition: there isn't a path from initial state "Start" to state "State 2" and thus it's impossible to cover "State 2" and it's outgoing transition. If you run test generation using //Optimal// on this model, you would get the following error message: | As you may have picked up the error in the model - it breaks the first condition: there isn't a path from initial state "Start" to state "State 2" and thus it's impossible to cover "State 2" and it's outgoing transition. If you run test generation using //Optimal// on this model, you would get the following error message: |
openOptima.NoSolutionException: Unable to reach following states from state 1: state 2 | openOptima.NoSolutionException: Unable to reach following states from state 1: state 2 |
| |
Most sequencers will report the above error except //Random// and //Concurrent// sequencers due to the nature how these two sequencers generate test sequence. | |
| |
Another commonly encountered issue with test generation is the use of transition guard. Transition guard is only used during automation as the variables used in guard condition will only be evaluated/set by automation script. During test sequence generation, you should assume that all transition guards will be ignored. | Another commonly encountered issue with test generation is the use of transition guard. Transition guard is only used during automation as the variables used in guard condition will only be evaluated/set by automation script. During test sequence generation, you should assume that all transition guards will be ignored. |