The Visual plan editor is the most basic and straight-forward way to create a Plan in Step. When using the Visual interface you create your Plan in a code-free intuitive editor that gives instant access to the libraries of available Keywords and Controls. Using the Visual interface makes it possible to create a Plan in an intuitive manner without technical skills and prior knowledge of Step. It is also well-suited for complex automation plans which require a visual representation of the Plan. Alternative options to the Visual plan editor are listed here

Creation

To create a new Plan using the Visual editor, log into the web interface of Step, navigate to Plans and click on the “New plan” button in the Plan view:

At the Plan creation, you need to select the type of Control for the root node of your Plan. By default a Sequence is selected, which is fine in most cases. For classical automation scenarios Step comes along with specific controls that add some specific features when used as root node of the Plan. Depending on your scenario following Controls might be selected as root:

• Functional test case: TestCase
• Functional test set (a set of test cases): TestSet
• Load test scenario: TestScenario
• Monitoring test case: TestCase
• Please refer to the plans page for an exhaustive list of available controls

Edition

When creating a new Plan or opening an existing Plan you’ll be redirected to the Plan editor. The Plan editor is structured as follow:

Plan tree

On the left side of the editor the plan tree is displayed. There you can interact with the nodes of the tree either using the top buttons, drag and drop gesture, “right-click” context menu or keyboard shortcuts.

The available operations are:

• select: to display the details of the node in the middle part of the editor
• move: reorganize the structure of your tree
• copy-paste: duplicate a node. You may paste the copied node into another plan given that you stay on the same browser tab
• delete: remove the selected node from the plan
• rename: rename the node
• open: open corresponding editor if any (i.e. for called plans and composite). Can also be triggered via double click
• disable/enable: disable the execution of this specific node and its children

These operations can also be applied on multiple nodes at the same time. To select multiple nodes, hold the control (Ctrl) key down to select nodes one by one or use the shift key for a range selection.

Node edition

When selecting a node in the plan tree the details of the node are displayed in the middle part of the editor.

Component library

On the right side of the editor access is given to the 3 types of libraries

• Controls: listing the available Controls
• Keywords: listing the registered Keywords
• Other plans: listing the Plans which might be referenced to build modular Plans

You can add as many nodes as you want by clicking the + buttons of the items shown in the different library tabs. They will then be automatically added to the currently selected node of the plan tree. Then, using drag and drop and the upper arrow and lower arrow buttons, you can reorganize nodes and place them in the order that you want:

Node common properties

All nodes share at least the following common properties:

• Name: used to define the name of the node.
  • This name is used by the tree view and for the generation of report nodes during the test executions
  • This name can be set dynamically using the groovy “lightning” toggle
• Description: optional field used to described the current node
• Instrument: defines if a node is intrumented or not. If a node is instrumented its execution time will be measured and a performance measurement will be produced after each execution of the node. The resulting performance measurements of type = “custom” can be visualized on the performance tab of the execution view
• Skip node execution: toggle to disable the execution of this specific node (and its child)
• Continue execution of parent element on error: defines if the execution of the parent sequence should continue when this node fails. Per default the execution of the sequence will stop in case of any error

Execution

To execute you’re plan, click on the play button located on the top of the editor. You’ll then be prompted for the start parameters. Per default there’s only one start parameter configured: Environment. The list of available start parameters can be extended and fully customized. Once the start parameters selected you have to choose the execution mode. 3 execution modes are available:

• Simulation: When running a Plan in the simulation mode, the plan is executed normally up to Keywords. In this mode Keywords aren’t executed but only “simulated” which means that they will be reported as PASSED with an empty output. This mode can be used to check the global execution flow of the Plan before executing it.
• Execution: This is the normal execution mode. In this mode both the plan and the keywords are executed.
• Scheduling: With this button you can schedule your plan to run it later or regularly.

Debugging (interactive session)

You can debug a plan and run it step by step using the interactive session of the visual plan editor. To start an interactive session click on the button Start interactive session located next to the execution button.

Once the interactive session started you can run each node by selecting it and clicking on the button “Run interactively”

Export

You can export and download a Plan from the Visual Plan Editor using the button Export located on the top of the editor. The plan is exported as a Step archive (sta) file which can be reimported in the the same instance or another instance of Step. To import a Plan navigate to Plans, click the import button on the top of the table, drag&drop the export file (artefact_export.json) and click the OK button. You should find the freshly imported plan in the plan list.

More details can be found in the dedicated page for Import and Export