Model-Based Testing For Web Applications With TestOptimal - (Part 4) Reports

Previous articles on Model-Based Testing For Web Applications With TestOptimal:

Part 1 - Preparing The Model
Part 2 - mScript
Part 3 - Generating Sequences

Today we conclude this series of articles on using TestOptimal for web applications testing by looking at the reporting features. TestOptimal provides detailed information on all aspects of each model-based testing project. The main reporting elements are:

1. Execution Status
2. Execution Progress
3. Testing Coverage: includes State/Transition traversals and # of each that are covered or left un-covered
4. Transition Sequences: a description of each state-to-state transition
5. Execution Details: includes exceptions and transition response times in milliseconds, as well as statistical analysis of the 3-sigma range for each response time on state/transitions based on historical MBT executions
   
6. Debugging: this information is provided in several panes - Console, mScript Log, Server Log and Selenium Log

Below is a report-by-report look at the information TestOptimal provides, along with a brief description for each report.

This is the Monitor Tab, which provides information on execution and coverage:

The Sequence Log tab shows the test sequence (state and transition traversal sequence) generated from the model with the selected sequencer. Use this transition log to find when and where the MBT exception occurred. You may also use this transition log to capture the test sequence and feed it to your testing frame work:

The Stats Tab shows MBT execution stats collected by TestOptimal, both in-progress MBT execution or historical executions:

The client log messages are written to this console log window. You can adjust the debug level using the drop-down list on top of the console:

The mScript Log window displays the log messages generated by your mScript and errors and exceptions triggered by the mScript:

The Server Log dislays the log generatd by TestOptimal sever. Ths is the place where you can find the errors and exception stack traces:

If you are using the bundled Seleninum RC server, this log window will let you access Selenium RC sever log file:

This concludes our 4 part series on using TestOptimal for model-based testing of web applications.  Although we covered the main steps that relate to model-based testing - create the model, customize the mScript, generate and execute test sequences, and analysis results - there's a lot more to be discovered with TestOptimal.  For more information on other features (e.g. mCase sequences, java support), different editions, and how to extend TestOptimal, visit their website here.  I highly recommend that you look at their various tutorials and examples to see just how extensive this tool is for model-based testing.