TestOptimal Wiki

»Menu: Model / Model Setting; »Model Editor MiniButton

MBT Settings contains the settings that affect the test case generation.

All settings have hover messages describing what the properties are. You can get to the hover message for the property by moving your mouse over the property label. Below are a more detailed description of these properties:

• Sequence Mode - required field, MBT sequencer to be used to generate the test sequences/steps from the model and execute your model.
• Objective - choice of Min Traversals or Min Cost, used by optimal sequencers. Min Traversals to generate minimum number of traversals (test steps) while Min Cost to generate test sequences that completes in least execution (elapse) time using the previously collected transition performance statistics. Default is Min Traversals. (Rel. 3.0)
• Coverage Type - choice of Transition or Paths. Select Transition to achieve coverage of all transitions at least once. Select Paths to explore the all combination of incoming transitions and outgoing transitions for each state. Default is Min Traversals. (Rel. 3.0)
• Random Seed - to initialize the random number generator used by Random Sequencer and Greedy Sequencer. If this field is set, it will cause the sequencer to use the same set of random number and thus same set of test sequences/steps will be generated. If not specified, a default seed will be used. You may dynamically change the set for each model execution by calling MScript function $setSeed('seedValue').
• Sequencer Parameters - parameters to be use by sequencers. e.g. MaxDup=3 for PathFinder sequencer to limit amount of variations in sequence paths. (Rel. 4.4.12)
• Stop Coverage - transition coverage when reached to stop MBT execution.
• Stop Req. Coverage - requirement coverage when reached to stop MBT execution.
• Coverage Type - option of transition coverage or path coverage. Coverage type works with Sequence Mode.
• Stop Count - integer, the number of transition traversals when reached to stop the MBT execution.
• Stop Time - integer, the number of seconds the MBT execution is allowed to run.
• Stop Path Count - integer, number of test cases (paths from initial state to final state) when reached to stop MBT execution.
• Stop Executions - integer, number of failures when reached to stop MBT executions.
• Stop at Final State Only - if MBT execution should stop at final state only.

The above Stop fields are used to control when the MBT execution should stop. They are ORed, that is, MBT execution stops when any of the condition is evaluated to true. If you are stress/load test your application, you may not want to set any of these fields except Stop Time.

• Iterations - integer, number of times to execute the model. This is usually used to conduct your load testing when you re-run again and again the model against your web application. If used with the Threads field, you can simulate multiple concurrent users (virtual users) running a set of scenarios simultaneously against your application. This setting is ignored by Random and Greedy sequencers for which you would set the stop conditions to control how long you want the execution to last instead.
• Iteration Delay - integer, number of milliseconds to wait between two consecutive iterations. This delay is also used to pause between the startup of two consecutive threads. (Rel 3.0.32)
• Threads - integer, number of testing threads to start to test your application. This is also called Virtual Users to stress and load test your application. If Threads is smaller than the Iterations, then the same thread may need to execute more than one iterations, in which case the Iteration Delay will be executed between the two iterations performed by the same thread.
• Thread Delay - integer, number of milliseconds to delay the startup of each thread. Use this setting to spread out the threads to avoid all threads trying to start at the same time that may overwhelm AUT.
• Shuffle Path - Yes or No, ignored by Random and Greedy sequencers. Set this field to Yes to instruct sequencers to shuffle the test cases before executing them. This is useful to create random sequence of test cases.
• Parallel Mode - Shared or Duplicate. This is ignored by Random and Greedy sequencer. When set to Shared, all threads (virtual users) will execute test cases from the same set of test cases generated from the model. If set to Duplicate, each thread (virtual user) will execute test cases from its own test case list generated from the model. Use Shared to achieve faster test coverage and use Duplicate to simulate multiple users using AUT.