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
ide_monitor [2020/05/04 15:15]
admin [Debug Expression] 		ide_monitor [2021/01/05 03:00] (current)
Line 2: Line 2:
 //Execution Monitor// monitors the model execution progress status and allows execution of debugging scripts. The execution stats include the execution status, estimation of execution progress % and model coverage.  //Execution Monitor// monitors the model execution progress status and allows execution of debugging scripts. The execution stats include the execution status, estimation of execution progress % and model coverage. 
  
-{{http://TestOptimal.com/img/IDE_MonitorTab.png?600x400}}+{{wiki:idescreen:ide_monitor.png?500}}
  
 ---- ----
Line 20: Line 20:
  
   * Status - model execution status, STARTED, PAUSED, ENDED or ERRORED.   * Status - model execution status, STARTED, PAUSED, ENDED or ERRORED.
-  * Virtual Users - number of virtual users (threads) specified in [[Execution Setting]].+  * Virtual Users - number of virtual users (threads) specified in //Execution Settings//.
   * Running - active virtual users (threads)   * Running - active virtual users (threads)
   * Start Time - model execution start date and time   * Start Time - model execution start date and time
Line 29: Line 29:
  
 ---- ----
-==== Debug Expression ==== +==== Debug Console====
-//Debug Expression// allows you to run scripts while the model is executing or execution is paused.  Script will be executed on a randomly selected virtual user (thread) if more than one is running.+
  
-The results from the script execution are displayed in JSON.+{{wiki:idescreen:ide_monitor_codeassist.png}}
  
-Be aware that if some of functions in //$SYS// may depend on the context of the thread. For example //$SYS.getCurState()// reports the current state. While model execution is paused, it may not have the state context established yet.+//Debug Console// allows you to run scripts while the model is executing or execution is paused.  If more than one is running, script will be executed on a randomly selected virtual user (thread 
 + 
 +Script editor is a simplified [[ide_script | Script Editor ]].  You can run the debug scripts in the following: 
 +  * run line - run script on current line 
 +  * run selected - run selected script lines or script expression 
 +  * run all - run all script lines 
 + 
 +The results from the script execution are displayed below the script editor. 
 + 
 +Be aware that some of functions in //$SYS// may depend on the thread context and thus will not return the correct result since your script will be running in a new thread. Below are the list of these functions in //$SYS//: 
 + 
 +  * getCurState 
 +  * getCurTrans 
 +  * getCurDataSet 
 +  * getCurTravUID 
 +  * getData 
 +  * setCurTransSatisfyingHint 
 +  * setTransGuardHint