https://step.dev/knowledgebase/30/userdocs/executions/ Recent content in Executions on Step Documentation Hugo -- gohugo.io en Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/executions/execution-reporting/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/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 Click to see on which agent(s) the plan was executed A list of execution parameters Displays a searchable table of all execution parameters Select the layout used to display the report Modify / create a custom report layout Test Cases If the executed plan contains more than one test case, a panel lists the status of each. https://step.dev/knowledgebase/30/userdocs/executions/legacy-execution-reporting/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/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/30/userdocs/executions/execution-housekeeping/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/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/30/userdocs/executions/execution-advanced/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/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/30/userdocs/executions/plan-reporting/ Fri, 21 Nov 2025 14:08:01 +0100 https://step.dev/knowledgebase/30/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/30/userdocs/executions/schedule-executions-reporting/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/executions/schedule-executions-reporting/ In this view, you can find reports aggregated across multiple executions of the same schedule. The main purpose of this view is to provide insights into whether scheduled executions have passed or failed over time. Schedule Name – The name of the scheduled task. Use quick-actions to configure the associated plan or schedule. Last Execution – The most recent time the schedule was executed and its result (pass/fail). The settings for automatic refresh and the time range to be shown.