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
Last revision Both sides next revision
ide_script [2020/06/01 15:14]
admin [Editor Overview] 		ide_script [2021/01/31 20:27]
admin [MCASES Script]
Line 10: Line 10:
   * auto formatting   * auto formatting
   * code collapse   * code collapse
-  * code assist+  * [[#code assist]]
   * search   * search
   * replace   * replace
Line 18: Line 18:
 {{ wiki:idescreen:ide_script_toolbar.png? 150 }} {{ wiki:idescreen:ide_script_toolbar.png? 150 }}
  
-//Ctrl-Space// opens code assist windows:+The info mini-button **i** gives more detailed information on these editor features. 
 + 
 +Click //P// to open a dialog to activate [[#Plugins]] for the model. 
 + 
 +---- 
 + 
 +==== Code Assist ==== 
 +Code assist is supported on [[https://testoptimal.com/v6/apidocs/|system functions and plugin functions]], which includes your own custom plugins. 
 + 
 +Code assist can be opened with //Ctrl-Space// in one of the following:
   * on a blank line or after a "$"   * on a blank line or after a "$"
-{{ wiki:idescreen:ide_script_ca.png? 80 }}+ 
 +{{wiki:idescreen:ide_script_ca.png? 80}} 
   * on chained system or plugin function calls   * on chained system or plugin function calls
-{{ wiki:idescreen:ide_script_ca_sys.png? 170 }} 
-  * on java classes 
-{{ wiki:idescreen:ide_script_ca_javaclass.png? 225 }} 
  
-The info mini-button **i** gives more detailed information on these editor features.+{{wiki:idescreen:ide_script_ca_sys.png? 270}}
  
-Click //P// to open a dialog to activate [[#Plugins]] for the model.+  * on java classes 
 + 
 +{{wiki:idescreen:ide_script_ca_javaclass.png? 225}}
  
 ---- ----
Line 178: Line 188:
 //MCASE Script// is where //MCase// are defined. //MCASE Script// is where //MCase// are defined.
  
-//MCase// is a custom test case / workflow that you defined explicitly for the system to generate a sequence path from the model to achieve specific scenario. +Often times you may have a set of specific test scenarios you want to make sure are covered to complement the system generated test cases.  You can achieve just that with //MCase// -  a custom test case / workflow that you defined explicitly for the system to generate a sequence path from the model to achieve specific scenario. 
  
 Consider your model as a map to //GPS//, //MCase// is just a set of way points you want to visit. When you execute //MCase//, a sequence  path (trip/route) is auto-generated from your model. Consider your model as a map to //GPS//, //MCase// is just a set of way points you want to visit. When you execute //MCase//, a sequence  path (trip/route) is auto-generated from your model.
Line 191: Line 201:
 ---- ----
 ==== User Script ==== ==== User Script ====
-Besides [[#TRIGGER Script]], [[#PAGES Sript]] and [[#STEPS Script]], you may also add additional scripts.+Besides [[#TRIGGER Script]], [[#PAGES Sript]], [[#STEPS Script]] and [[#MCASE Script]], you may also add additional scripts.
  
 To create a user script, click on "+".  You can rename the script by clicking on the pencil mini-button. To create a user script, click on "+".  You can rename the script by clicking on the pencil mini-button.
Line 210: Line 220:
       $SYS.log('multiplying 10 and 20: ' + $MyScript.multiply(10, 20));       $SYS.log('multiplying 10 and 20: ' + $MyScript.multiply(10, 20));
    }    }
 +
 +----
 +==== Include File ====
 +You may include script file into your TRIGGER script.  Just add the @INCLUDE_FILE below:
 +   @INCLUDE_FILE 'absolute file path to include file'
 +
 +The above script will literally inject the content of the included file into current script before TRIGGER script is executed.  
 +
 +The side effect of using this INCLUDE_FILE is that the injected scripts will mess up the script line # reported on errors.
  
 ---- ----