Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
ide_model [2020/06/10 18:12]
admin [Modeling Canvas] 		ide_model [2021/01/01 02:31]
admin [Transition Properties]
Line 34: Line 34:
  
 The mini buttons in tool pallet are divided into three groups: The mini buttons in tool pallet are divided into three groups:
-  * ★ edit and move states/transitions and edit properties +  * ★ edit / move states/transitions and edit properties
-  * ☆ mark / select states/transitions for set operations+
   * O add states and transitions   * O add states and transitions
 +  * ☆ mark / select states/transitions for set operations
  
-You will also notice that the background for the modeling canvas changes for each model: white, blueish and pinkish.+You will also notice that the background for the modeling canvas changes for each mode: white, blueish and pinkish.
  
 === Creating New States === === Creating New States ===
Line 90: Line 90:
   * toggle breakpoint,    * toggle breakpoint, 
   * highlight incoming and outgoing transitions with different color and auto re-route all incoming and outgoing transitions.   * highlight incoming and outgoing transitions with different color and auto re-route all incoming and outgoing transitions.
 +  * open trigger (script)
    
 {{wiki:idescreen:ide_model_menustate.png?100}} {{wiki:idescreen:ide_model_menustate.png?100}}
Line 100: Line 101:
   * re-route transition   * re-route transition
   * change source and/or target states   * change source and/or target states
 +  * open trigger (script)
  
 {{wiki:idescreen:ide_model_menutrans.png?100}} {{wiki:idescreen:ide_model_menutrans.png?100}}
Line 129: Line 131:
   * State ID - required, a unique identifier assigned to the state in the model   * State ID - required, a unique identifier assigned to the state in the model
   * Description - a freetext description   * Description - a freetext description
-  * Sub Model - sub-model attached to the state+  * Sub Model Name - sub-model attached to this state 
 +  * Data Set - data set attached to this state
   * Color* - background color, custom class, or css style in json, e.g. {"background": "yellow"}   * Color* - background color, custom class, or css style in json, e.g. {"background": "yellow"}
   * Text Color* - state label color, custom class, or css style in json, e.g. {"font-style": "italic"}   * Text Color* - state label color, custom class, or css style in json, e.g. {"font-style": "italic"}
Line 152: Line 155:
   * Hide Name - not to display transition name on model and graphs   * Hide Name - not to display transition name on model and graphs
   * Description - a freetext description   * Description - a freetext description
-  * Color - transition line segment color, custom class name, or css style in json, {"background": "green"}. +  * Transition Color/Style: 
-  * Text Color* - transition label color, custom class name, or css style in json, e.g. {"font-style": "italic"}+    * Line - transition line segment color, custom class name, or css style in json, {"background": "green"}. 
 +    * Label* - transition label color, custom class name, or css style in json, e.g. {"font-style": "italic"}
   * Weight - weight (importance), transitions with higher weight will likely be traversed more often by Random sequencer   * Weight - weight (importance), transitions with higher weight will likely be traversed more often by Random sequencer
 +  * Data Set - data set attached to this state
   * Traversal Required - minimum number of times the transitions must be traversed. Default 1. Set it to 0 for transitions are required to be traversed (tested).   * Traversal Required - minimum number of times the transitions must be traversed. Default 1. Set it to 0 for transitions are required to be traversed (tested).
   * Guard - boolean expression, transition can  not be traversed until this condition evaluates to true    * Guard - boolean expression, transition can  not be traversed until this condition evaluates to true 
Line 194: Line 199:
 ==== Model Execution ==== ==== Model Execution ====
 There are three ways to execute the models: There are three ways to execute the models:
-  * run - normal execution of the model+  * generate test cases/paths without executing scripts 
 +  * run - normal execution of the model to generate test case and execution of automation scripts
   * debug - step through the model to debug   * debug - step through the model to debug
   * play - visualize model execution synchronized with AUT / target process   * play - visualize model execution synchronized with AUT / target process
  
 This can be accomplished with the shortcut buttons: {{wiki:idescreen:ide_run_btns.png?100}}: This can be accomplished with the shortcut buttons: {{wiki:idescreen:ide_run_btns.png?100}}:
-  * Run +  * {{wiki:idescreen:ide_model_btn_gen.png?16}} Gen 
-  * Stop +  * {{wiki:idescreen:ide_model_btn_run.png?16}} Run 
-  * Pause +  * {{wiki:idescreen:ide_model_btn_stop.png?16}} Stop 
-  * Step Over +  * {{wiki:idescreen:ide_model_btn_pause.png?16}} Pause 
-  * Debug - run and pause on initial state +  * {{wiki:idescreen:ide_model_btn_step.png?16}} Step Over 
-  * Play+  * {{wiki:idescreen:ide_model_btn_debug.png?16}} Debug - run and pause on initial state 
 +  * {{wiki:idescreen:ide_model_btn_play.png?16}} Play
  
 Model execution can be monitored with [[ide_monitor | Execution Monitor ]]. Model execution can be monitored with [[ide_monitor | Execution Monitor ]].