The driver uses a handful of simple control commands.
LOAD:<filename relative to project root folder>
This instruction tells the driver to load an automation script.
This instruction is especially useful when debugging a script because it instructs the driver to stop loading more commands from the script currently under execution.
- command 2:
- command 3:
Here executed steps are 1, 1.1, 1.2, and 1.3. Thus command 1.4 and EXIT: are left out.
This instruction tells the driver to not only stop executing from this point on, but furthermore, to stop the automation thread too. This might also be handy during script debugging.
Instructs the driver to wait for the provided time in milliseconds.
120000 milliseconds equals 2*60*1000, resulting in a 2 minuts wait.
Instruction that tells the driver to stop waiting for user signal to continue. Please note that no input eventually will conflict with the overall driver timeout.
PAUSE:Push a button to continue...
Pressing the <enter> button makes the script continue.
Instruction for overriding the default timeout, which is 10 minutes or 600 seconds. The timeout can be seen as the execution window for each command. When a timeout occurs, the report will show this as an INTERRUPT state and a orange breadcrum trace.
Every command can be preceded by a description block. It is suggested to used it and to spend some time on writing meaning full description which will make it a lot easier to interpretate the final report.
/* * This is a comment which will go into the html report. * and it can span multiple lines */
This instruction tells the driver that it meets an advanced command that needs to be interpretated as some language type.
This example will just execute an empty advanced command.
Script files should be encoded as ansi or ISO-8859-1.
The driver and its plugins can show command syntax if implemented.
Use either the command ?: or ?:<plugin>.