Scripts can be authored and tested interactively. This means commands can be added and executed individually to varify if they provide the intended purpose. A script only needs at least a single line to permit interactive testing.
To test a script it is necessary to click the Goto Start button, which places an execution carot on the first line (a green triangle pointer). When the execution carot appears on a command line, that is the command that will be executed when the Single Step button is clicked. Once executed, the carrot changes to a green check mark as a reminder of commands executed.
Whenever Goto Start is re-clicked, all execution check marks are cleared. All execution marks are also cleared when Stop is clicked. All execution marks are also cleared when a script repeats (Repeat enabled, and RepeatTimer reaches zero).
Clicking Single Step executes commands one at a time while implications can be interactively be viewed, monitored, or verified on other panels. Since script commands provide the means for automating the same program functions that can each by performed manually on various panels, the same panel feedback is provided as if the user had performed the manual activation, with a single notable exception. Some program feedback is intended solely as informational ... such as when communication query times out vs when normal reply is received. Such informational feedback is supressed when scripts are run automatically, but provided for manual action or single step testing.
Most variables can be manually edited (only a few variables do not permit user modification) permitting program behavior that is shaped by variable content to be tested at will during Single Step execution.
Program execution will resume from the current carot position when Resume is clicked. Likewise automatic program execution can be interrupted with the Pause button with execution check marks and carot indicating execution path and current execution position.
ScanEngine Explorer permits the user to add, delete, or edit script commands during Single Stepping execution, within limits. The position of the green execution carrot is kept track. As long as commands are inserted, deleted, or edited ahead of the execution carrot, new or altered commands can be single-stepped into. However, should commands be added or deleted behind the current execution carrot, ScanEngine Explorer will detect whenever the carrot is not in the anticipated location. Should this happen simply click Goto Start and begin Single Step from the beginning whenever changes are made to commands already executed. Note that clicking Goto Start is always the most secure means of testing after changes as it is readily possible to imagine changes which alter program around the current execution carrot without altering it's location. However, interactively adding program in advance of the current execution carrot is readily permitted.