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_script [2020/05/28 02:21]
admin [ShortCut Keys] 		ide_script [2024/01/02 19:28] (current)
admin [Plugins]
Line 10: Line 10:
   * auto formatting   * auto formatting
   * code collapse   * code collapse
-  * code assist+  * [[#code assist]]
   * search   * search
   * replace   * replace
Line 16: Line 16:
  
 The tool pallet on the upper-right corner of the editor gives you quick access to common editor features. The tool pallet on the upper-right corner of the editor gives you quick access to common editor features.
- 
 {{ wiki:idescreen:ide_script_toolbar.png? 150 }} {{ wiki:idescreen:ide_script_toolbar.png? 150 }}
  
Line 22: Line 21:
  
 Click //P// to open a dialog to activate [[#Plugins]] for the model. 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 "$"
 +
 +{{wiki:idescreen:ide_script_ca.png? 80}}
 +
 +  * on chained system or plugin function calls
 +
 +{{wiki:idescreen:ide_script_ca_sys.png? 270}}
 +
 +  * on java classes
 +
 +{{wiki:idescreen:ide_script_ca_javaclass.png? 225}}
  
 ---- ----
Line 31: Line 48:
 Activated plugins will automatically added to code assist (Ctrl-Space). Activated plugins will automatically added to code assist (Ctrl-Space).
  
-More info can be found at [[Plugins]] and [[http://testoptimal.com/v6/apidocs/ | System and Plugin Functions]].+More info can be found at [[Plugins]] and [[http://testoptimal.com/v7/apidocs/ | System and Plugin Functions]].
  
 ---- ----
Line 171: 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 184: 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 203: 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.
  
 ---- ----