Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
statenode [2020/05/04 18:30] admin removed |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== State/Node Property ===== | ||
- | //>> | ||
- | Each // | ||
- | |||
- | |||
- | {{http:// | ||
- | |||
- | ---- | ||
- | ==== 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" | ||
- | |||
- | * 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 " | ||
- | * 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/ | ||
- | * 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/ | ||
- | * Tags - requirements id or any identifier for requirements traceability. Stats (traversal and pass/ | ||
- | * 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/ | ||
- | * 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' | ||
- | * 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 // | ||
- | * 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 // | ||
- | |||
- | |||
- | Click on the button " |