Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
tutorial:debugging [2020/07/19 16:15] admin [Debugging test generation] |
tutorial:debugging [2020/12/31 18:48] admin [Debugging automation script] |
||
---|---|---|---|
Line 26: | Line 26: | ||
The sequencer used is shown on application toolbar on the upper-left corner of the IDE. Make sure that the expected sequencer has been chosen. | The sequencer used is shown on application toolbar on the upper-left corner of the IDE. Make sure that the expected sequencer has been chosen. | ||
+ | ==== Missing transitions ==== | ||
In order for the sequencers to be able to generate test sequences from the model, the following conditions must hold true for all models: | In order for the sequencers to be able to generate test sequences from the model, the following conditions must hold true for all models: | ||
* there must be a path from initial state to every state in the model | * there must be a path from initial state to every state in the model | ||
Line 36: | Line 37: | ||
| | ||
- | Most sequencers will report the above error except //Random// and // | + | ==== Transition guards not working ==== |
Another commonly encountered issue with test generation is the use of transition guard. | Another commonly encountered issue with test generation is the use of transition guard. | ||
+ | ==== Test case too long ==== | ||
+ | A test cases is represented as a path from the initial state to a final state. | ||
+ | |||
+ | If you wish to get a set of shorter test cases, you may choose // | ||
Line 47: | Line 51: | ||
===== Debugging automation script ===== | ===== Debugging automation script ===== | ||
+ | |||
+ | Automation scripts are called as model executes. If your automation script is not functioning as expected, you may try any of the following methods to trouble-shoot the problem: | ||
+ | * check //Server Log// file if receiving runtime errors | ||
+ | * add additional debugging messages and check //Script Log// file | ||
+ | * pause model and check if AUT is at the expected state | ||
+ | * dynamically execute scripts and validate the results | ||
+ | * highlight script and press //Ctrl-E// | ||
+ | * execute script in //Monitor// tab | ||
+ | |||
+ | |||
+ | |||
===== Debug console ===== | ===== Debug console ===== |