Use the Toolbox

Toolbox contains the scenario tree, an action form, the target display or terminal, logs and collected output. Its startup bar follows actual opening milestones; it disappears when startup completes or fails. Resize or collapse panes to concentrate on the current task.

Apply, cancel and save

Select or add an action, edit its form, then choose Apply action. This commits the validated action to the in-memory scenario. Cancel discards that form edit. Adding an action does not insert it just because you selected a type.

If you change action, Play, edit source or leave with unapplied changes, choose Apply action, Discard changes or Keep editing in the prompt. Apply is separate from the Toolbox Save, which persists the Job.

Use Undo/Redo for applied scenario edits, moves and source changes. Undo does not reverse a website click, submitted form, generated file or command execution. Text controls keep their own typing history; scenario history is local and bounded.

The JSON command opens the same scenario’s source in a separate window. Correct invalid JSON before using the tree. Closing the source window neither saves the Job nor closes Toolbox.

Debug and loop playback

Debug defaults on and is remembered in this browser. With Debug on:

• Scenario Play executes ordinary actions and advances each reached outermost While or Repeat On once.
• Playing that loop again advances its next iteration. Nested loops complete within the selected outer iteration.
• A child can be tested using an available retained loop context. Its required parent must actually have been reached.
• An exhausted loop does not wrap to its first item. Use Restart loop or Restart scenario iterations deliberately.

Loop-source or parent-scope changes can require a restart. Changing a body does not automatically reset progression. A failed body may already have consumed the selected item; inspect the current context before advancing.

Turn Debug off to execute the full submitted scenario or subtree, with ordinary full loop traversal. This does not create a Session or reset the page and variables. Ordinary Session runs always use full traversal, independently of this Toolbox switch.

Whole scenario or subtree

Row Play submits that action and its children. It does not run preceding siblings or reconstruct missing ancestors. A field action that needs an active collection row cannot be tested as an unrelated root action.

Toolbox retains its page and variables between commands. Start URL runs when the environment opens, not before each Play. A fresh Session must include the navigation, initialization and waits that your interactive test may already have performed manually.

Internal Subsessions can be tested in Toolbox. External Subsessions launch ordinary work and are unavailable from Toolbox; test them through an ordinary Session instead.

Inspect targets and choose points

For Browser locators, choose CSS, Text or XPath before requesting proposals. Inspect the proposed selector and match count, adopt it explicitly, then Apply the action. Inspection does not save or execute it.

Field previews can show matches relative to their Container parents. A temporary parent-row choice helps inspect one row without rewriting the saved Container selector. Read partial/sample indicators; a preview is not a complete dataset or a future uniqueness guarantee.

Browser and Desktop Linux coordinate pickers take a point from the visible display. The selection gesture chooses coordinates without issuing the corresponding remote click. Escape cancels picking. Apply the resulting numbers before Play.

Console uses terminal output/input rather than a graphical display. Desktop points are not Browser selectors. See Robot kinds.

Values, logs and files

Toolbox previews collected records without publishing them to project Data, even with Push data enabled. The current values view is bounded; its visible recent rows are not necessarily every row from a long test.

Temporary generated files can be opened/downloaded when the row offers that command and your current Toolbox rights permit it. They expire when the environment closes and can be evicted as more output is produced. Preview only without an active command remains metadata, not a downloadable saved file. See Files.

Stop, close and recover

Stop interrupts the current command without undoing earlier external effects. Closing the owning Toolbox terminates its interactive environment; minimizing the editor is different from closing it. Save before leaving if you need the Job changes, and download temporary files you need to keep.

A recovered local draft restores source, not a running page, execution history or temporary files. Review it against the latest saved Job before saving. Use current diagnostics rather than assuming general breakpoints or automatic recording are available.