https://step.dev/knowledgebase/31/categories/execution/ Recent content in Execution on Step Documentation Hugo -- gohugo.io en Mon, 19 Oct 2026 00:00:00 +0000 https://step.dev/knowledgebase/31/devops/automation-package-cli/step-cli/local-execution/ Wed, 22 May 2024 14:08:01 +0100 https://step.dev/knowledgebase/31/devops/automation-package-cli/step-cli/local-execution/ The Step CLI can run an entire Automation Package on your own machine, without a Step server. It uses a local agent provisioning which provisions the required agents as separate processes. The Keywords therefore run in the same isolation, and against the same agents, locally and centrally. An agent is started the first time a Plan needs it, and is then kept running and shared by all the Plans the command executes, until the command ends. https://step.dev/knowledgebase/31/devops/step-studio/ Mon, 19 Oct 2026 00:00:00 +0000 https://step.dev/knowledgebase/31/devops/step-studio/ Step Studio brings the visual editors of the Step platform to your local machine. It lets you create and maintain Automation Packages, execute Plans locally, and execute or deploy your automation on a remote Step instance. Studio works directly on the Automation Package files in your project, including its YAML descriptor and Plan fragments, alongside the source code and resources used by your Keywords. You can use Studio and your IDE on the same project without maintaining separate copies of the automation. https://step.dev/knowledgebase/31/userdocs/executions/execution-reporting/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/executions/execution-reporting/ This page describes the new Execution Report page. You can choose to use the Legacy Execution Report page instead. (read more) Note: The Execution Report will automatically revert to the legacy page for executions prior to Step 27. The Execution Report provides insight into an ongoing or already concluded execution. The following general information is shown at the top: The current status of the execution The name of the executed plan A link to the plan The date when the plan was executed The user who initiated the execution Click to open a table of all resolved parameters You can find the provisioning logs here Click to see on which agent(s) the plan was executed A list of execution parameters Displays a searchable table of all execution parameters The currently shown report layout Click to switch to other layouts (“Execution Summary” is the default layout shipped with Step) Create a new blank layout Modify the selected layout Edit the layout (allowing to move, add or remove widgets) Duplicate the layout - creates a new layout filled with the selected layouts widgets - ideal when you want to modify a read-only layout Download the layout - this enables admins to copy a layout to Steps default layouts (advanced) Delete the layout Test Cases If the executed plan contains more than one test case, a panel lists the status of each. https://step.dev/knowledgebase/31/userdocs/executions/legacy-execution-reporting/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/executions/legacy-execution-reporting/ The legacy Execution Report page will be deprecated starting with Step 30. Executions give you an insight in the results of an executed Plan as well as the ability to detect and analyze errors, both within the Plan or the system tested / automated with it. Execution steps On the Execution list view, clicking on the Plan name of an Execution redirects you to the details of that execution. The Execution steps view shows the details of the executed Plan, as shown in the following screenshot. https://step.dev/knowledgebase/31/ai/mcp-server/tools/ Mon, 29 Jun 2026 00:00:00 +0000 https://step.dev/knowledgebase/31/ai/mcp-server/tools/ Reference for all tools exposed by the Step MCP Server. For setup and installation, see Getting Started. All tools accept two optional shared parameters: profile (which Step instance and credentials to use) and project (which project to act on). The discovery tools below are the exception: they don’t require a project. When omitted, parameters fall back to the configured defaults (see Profile and project resolution). Every tool’s response includes a resolvedContext block reporting the profile, baseUrl, and project actually used. https://step.dev/knowledgebase/31/devops/automation-package-cli/step-cli/ Wed, 22 May 2024 14:08:01 +0100 https://step.dev/knowledgebase/31/devops/automation-package-cli/step-cli/ The Step CLI (Command Line Interface) is used for all operations with Step. It provides an integration with the Step server and an easy way to integrate Step with a CI/CD pipeline. Currently it is limited to the operations related to Automation Packages but might be extended in the future. For Java specific projects, the CLI is also available as a Maven plugin. The CLI also includes Step Studio for creating and editing Automation Packages visually on your machine. https://step.dev/knowledgebase/31/userdocs/executions/execution-housekeeping/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/executions/execution-housekeeping/ If Automatic housekeeping is ON, you may want to flag the executions to be retained by the housekeeping job. To do that, toggle the Retain this execution and provide the information about your execution in the Description textbox - for example, information about a referenced execution that’s part of an overall test release. On the other hand, if you don’t want to retain this specific execution, you may directly delete it within the same pane: https://step.dev/knowledgebase/31/userdocs/executions/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/executions/ An Execution represents the result of a specific run of a Plan. It contains comprehensive information about the Keywords and controls within an executed Plan, including status, output values, performance measurements, and more. Executing a Plan You can run a Plan, and create a new corresponding Execution by clicking the “play” button available in the Plan list, Keywords list and the Plan editor: This will display the following Execution panel, specifying the Execution environment and the Execution mode. https://step.dev/knowledgebase/31/userdocs/executions/execution-advanced/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/executions/execution-advanced/ Performance optimizations For load test executions with extreme high load, depending on your system capacity, creating and persisting a report for each and every node execution will impact the maximum load your Step scenario can generate. In such cases, it is possible to disable the persistence of the nodes by setting one or more of the listed predefined variables, in the case of using a set control): tec.execution.reportnodes.persistbefore = false: This only persist the node state after its execution; thus you won’t see the nodes in RUNNING state but will have all information needed for your analysis and reporting. https://step.dev/knowledgebase/31/userdocs/agent-provisioning/ Mon, 30 Sep 2024 00:00:00 +0000 https://step.dev/knowledgebase/31/userdocs/agent-provisioning/ When running in Kubernetes, Step supports automatic provisioning of Agents (i.e. automatic provisioning of the containers responsible for executing Keywords) across multiple Kubernetes clusters. This page explains how to utilize Agent provisioning in Plans. For information on enabling or configuring Agent provisioning, please refer to the Agent Provisioning configuration page. How it works In a nutshell, the automatic Agent provisioning works as follows: Upon execution, Plans are scanned to determine the required Agents for execution Based on the calculation and the available Agent pools, the optimal number of Agents per Agent pool is calculated The required Agents are provisioned across the clusters of the selected Agent pools Once the Agents have joined the grid, the execution starts After execution, the agents are de-provisioned Configure provisioning settings in Plans When Agent provisioning is enabled in Step, users can configure the Agent provisioning settings in each plan (in the UI and in the automation packages). https://step.dev/knowledgebase/31/userdocs/executions/plan-reporting/ Fri, 21 Nov 2025 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/executions/plan-reporting/ In this view, you can find reports aggregated across multiple executions of the same plan. The view shows the same content as the Scheduled Execution Reporting View, but considers both scheduled and manual executions of the selected plan. It can be accessed via the Plan List “Open plan report” action. https://step.dev/knowledgebase/31/userdocs/ Wed, 13 Feb 2019 00:00:00 +0000 https://step.dev/knowledgebase/31/userdocs/ This section groups the documentation related to the use of Step. If you’re using Step for the first time, it is recommended to get started with on the tutorials