Differences

This shows you the differences between two versions of the page.

--- ide_stateprop [2020/05/04 19:23]
admin
+++ — (current)
@@ Line 1: / Line 1: @@
-===== Property Description=====
-A state usually represents a web page or a web page. To create a state, right mouse click on [[modelNode|modelNode]] and select "New State". Fill in the properties in [[PropertyTab|Property Tab]] as described below.
-  * State ID - required, a unique identifier you assign to this state. It must be unique for the entire model (all states including children states). It can not contain any spaces, dash "-" or any characters that are not valid for a java method name.
-  * Description - a freetext description to document what this state is about or represents.
-  * Initial State - required, to specify if this state is an initial state of your model, this is usually the first login page or welcome page of your application. There should only be one initial state for each model and each super state/submodel. Initial state is shown with a double ellipse.
-  * Final State - required, to specify if this state is a final state for the model. There should only be one final state within each super state/submodel so that you can control where your testing will end at. The final state is shown with a double octagon.
-  * Tags - requirements id or any identifier for requirements traceability. Stats (traversal and pass/failure) are automatically collected. If the state has tags entered, a link "show tags" will appear next to this field.
-  * Assert ID - the defect identifier to be used to raise the defect in ALM when the state failed, requires ALM plugin and configuratio.
-  * Reset URL - for web applications to be used to load the web page when the testing script failed. This allows the testing to continue from the correct page.
-  * Entry Delay(ms) - number of milliseconds to delay before executing the onEntry trigger.
-  * [[submodel|Sub Model Name]] - optional, sub-model attached to this state. (new in release 3.0)
-  * Sub Model Prefix - optional, a prefix to be added to all sub-states to ensure the state id are unique within the current model.
-  * Sub Model Filter - optional, filter sub model states and transitions by state/transition id (exact match or regular express) or stereotype. For example. mcase(mcasName); removeState(stateid); optionalState(stateid); removeTrans(transid); optionalState(tranid); traverseTimes(transid, n). You may use regular expression to match state/trans id by pre-fixing regular expression with "/" character (note "/" character will be removed before performing regular exprsesion match).
-  * Sub Model Sequencer - optional, select a sequencer to be used to generate test cases for the sub model. Leave it blank to use main model's sequencer.
-  * Pass-Through SubModel - Yes/No, if each pass through sub model must exit back to the main model. You must set the Traversal Times property for the incoming transition into the sub model state accordingly to achieve the sub model traversal.
-  * Color - optionally you can choose a background color for this state on the graph.
-  * Activate Type - type of condition when state is activated. This is for Enterprise Edition only. Select from the following options:
-    * Traversal Count - activates when expected number of transition traversals is reached (Activate Threshold)
-    * Transition Count - activates when expected number of distinct transitions are traversed (Activate Threshold)
-    * By setting path var //_activateState// - activates when the path variable //_activateState// is set to non-blank value. This path var is reset to blank after each state activation.
-    * Sum of transition weights - activates when sum of the weights from the transition traversals reaches the Activate Threshold.
-  * Activate Threshold - threshold value for Activate Type. This is for Enterprise Edition only.
-  * Trigger Trans - how transitions is/are triggered when the state is activated. This is for Enterprise Edition only:
-    * Random - randomly select one transitions\ from all outgoing transitions. Transitions must have guard conditions evaluated to true if guard conditions are defined.
-    * All - all transitions are triggered
-    * Set by //_triggerTransName// - name of the transition to be triggered is specified in the path variable //_triggerTransName//
-Click on the button "OK" to save the changes.
-====Concurrent System Modeling====
-Concurrent modeling is used to model concurrent systems or event/message driven systems such as embedded systems. It allows multiple transitions to be executing concurrently and complex logic to determine when a state can be activated (fired) and which of the outgoing transitions can be triggered/executed.
-====Activate State====
-In concurrent models, a state can be activated in several ways:
-  - number of incoming transition traversals exceeded the threshold value
-  - number of distinct incoming transition exceeded the threshold value - multiple traversals for same transition are counted once
-  - total weight of all incoming transition traversals exceeded the threshold value
-  - activated by [[http://testoptimal.com/javaDoc/reference/com/webmbt/plugin/LoadPlugin.html|MScript functions]]
-----
-====Execute Transition====
-Once the state is activated, transitions are triggered in several ways. Only transitions without guard condition and transitions with guard conditions evaluated to true can participate this operation.
-  - all outgoing transitions
-  - random selection of one transition from the outgoing transitions
-  - the transition with name matching the value of path var //_triggerTransName//
-  - triggered by [[http://testoptimal.com/javaDoc/reference/com/webmbt/plugin/LoadPlugin.html|MScript functions]]