Model Property

»Model Context Menu: Model Property; »Menu: Model / Model Property; »Model Editor MiniButton

Model Property dialog displays model properties. The properties are divided into several categories. Model properties are often used with or related to MBT Settings.

testoptimal.com_img_scxmlproperty.jpg


General Properties

  • Model Name - the name of the model. Must not contain space, dash/minus (-) or any punctuation symbols. To rename the model, use “File” / “Rename” menu.
  • Description - freetext description of your model. You will find “Description” field on every level of your model nodes.
  • AUT URL/File Path - url or file path of the application under test (AUT). Leave this field blank if the model is for user interface testing. If you are using multiple plugins you may enter one AUT URL/File Path for each plugin by prefixing the URL/File Path with the plugin id and colon and separate the multiple URLs/File Paths with semi-colon.
  • Browser Type - type of browser to be used to run your application. Select from the dropdown list. Please note the behaviour difference between SELENIUM and HTMLUMNIT plugin. If you are using SELENIUM plugin, the selected browser will be launched to run your application. If you selected HTMLUNIT, the browser type will be sent to your web application to allow your web application to be able to differentiate clients running on different browsers.
  • Auth Users - list of user ids which are allowed to access this model if the security is enabled. User ids must be separated by a semi-colon (release 3.0).

Model Versions

  • Model Version - user maintained version number for the model. This field is readonly when model is archived and open on Runtime server.
  • Model Build Number - system maintained sequential number, each time the model is archived, this build number is increased by 1.
  • From TestOptimal Ver. - The version of TestOptimal this model was last modified with.
  • Req. Version - the version of the requirements. This is user maintained field.
  • AUT Version - the software version of application under test (AUT). This is user maintained field. It is set to readonly when the model is archived.
  • Backup Date - readonly field, the date and time when the last backup was taken for this model.

Integration Properties

  • UI Map URI - file path or url pointing to UI Map list file

Execution Controls

  • Suppress Verify - to bypass any failures to allow model to run to completion. This is used for load / stress testing which focuses on performance.
  • Suppress Submodel Verify - to bypass any failures raised by any mscript from the submodel.
  • Trans Log Size - integer, maximum number of rows (state and transition traversals) to be stored in TransLogTab. Bigger number will consume more JVM heap memory and may slow down the display. It is recommended to start with a smaller number and increase it as you need to.
  • History Stats - integer, maximum number of stats for the past MBT executions to be kept. Professional Edition has a limit of 5 while Enterprise Edition has no limit. However bigger number may slow down the opening of the model.
  • Plugin - choose the right plugin to drive your application: Selenium, JavaApp, RemoteTriggerPlugin and RemoteCommandPlugin (for complete list of plugins, see Plugins). You may leave it blank if you just want to generate test sequence or generate testing script for offline testing, e.g. generate VBS script for testing with QTP. You may choose more than one plugins to execute the model by setting a sequential number. The plugins will be executed in the order specified.
  • Java Class/Groovy Scrip - java class path or groovy script path
    • writing test script in java code WriteHandler, enter the java class name including the java package path in this field. The java .class file must be stored in /classes/ folder and must be stored in the appropriate subfolder that reflect the java package path.
    • generate link generates a skeleton java code directly from your MBT model and all you need to do is fill in each method with your code.
    • enter groovy script file path that contains triggers for the model. You must have Groovy installed.
  • Action Delay(ms) - number of milli seconds to delay after the transition's action trigger is executed. Use this field to slow down the testing if your web application is experiencing strange and/or sporadic problem. This is especially problematic for web applications which use ajax to create or change dynamic content. You may override this setting in the transition property.
  • MScript Delay(ms) - number of milliseconds to delay after each mscript statement.
  • Test Output File - name of the output file to write out the test sequence by SeqOut plugin or by the <seqout> tag and xml comments <!– comments…–> (see Output Comment field). Use .tsv for tab delimited file, .html for web app and .txt for text file.
  • Output Comment - if system should automatically write mscript/xml comments into Test Output File file.
  • Initial Variabls: to set initial value for the user variables using the following format: var1=val1;var2=val2;…

Graph Preference

  • Graph Orientation - choice of Left→Right and Top→Bottom. Left→Right tells the graph generator to layout the states from left to right and thus making the graph wide. Similarly Top→Bottom will cause the graph to be layout vertical from top to bottom making the graph taller. The graphing is only available in Windows.
  • Color - a dropdown list to choose a background color for your model.
  • Expand Submodel - if the model graph should include details of the submodel.
  • Expand Submodel - if the submodel should be expanded on the model graph.
  • Use Short Label - to show minimal information of the transition on the graph