<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Load Testing on Step Documentation</title>
    <link>https://step.dev/knowledgebase/31/categories/load-testing/</link>
    <description>Recent content in Load Testing on Step Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 08 Jul 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://step.dev/knowledgebase/31/categories/load-testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Plan library</title>
      <link>https://step.dev/knowledgebase/31/libraries/plans_lib/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/libraries/plans_lib/</guid>
      <description>All of the plans documented in this section can be downloaded and then imported into your own private instance by following this procedure.
Basics Here are a few basic, yet non-trivial plans which will help you get started with the most useful and common constructs. We will be practicing with a very simple source type called &amp;ldquo;Json String&amp;rdquo;, which will help us distribute data across iterations and threads.
We can pass an arbitrary array of Json objects and then access them object by object.</description>
    </item>
    
    <item>
      <title>Agent Sizing Guide</title>
      <link>https://step.dev/knowledgebase/31/setup/configuration/agent-sizing/</link>
      <pubDate>Tue, 08 Jul 2025 00:00:00 +0000</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/setup/configuration/agent-sizing/</guid>
      <description>Agents are responsible for executing automation (automated test, load test, etc) through Keywords. Their resource requirements can vary significantly depending on the type of automation, the automation tools used, and the nature of the application under test. This guide provides practical recommendations to help you size agents effectively for reliable, stable, and performant execution.
For the general platform requirements and sizing recommendations, refer to the Requirements page.
Why Agent Sizing Matters Properly sizing your agents is critical for ensuring predictable and efficient automation execution.</description>
    </item>
    
    <item>
      <title>Controls</title>
      <link>https://step.dev/knowledgebase/31/userdocs/plans/controls/</link>
      <pubDate>Thu, 23 May 2019 07:00:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/userdocs/plans/controls/</guid>
      <description>Step supports a wide range of so-called controls to build-up complex flows in Plans. The supported controls range from classical control structures (like if blocks, loops, etc) to use-case specific controls like thread groups for load-testing, data-sets, etc. This page provides details about all the controls supported by Step.
General controls Set The Set control allows to define a variable and assign it a value. Variables defined with Set controls can be accessed according to their scope throughout Plans and sub Plans.</description>
    </item>
    
    <item>
      <title>Cypress Plugin</title>
      <link>https://step.dev/knowledgebase/31/plugins/cypress/</link>
      <pubDate>Wed, 10 Apr 2019 14:24:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/plugins/cypress/</guid>
      <description>This page describes how to install, configure and use the Step plugin for Cypress. The Cypress plugin allows you to declare Step Keywords that run Cypress specs or commands and thus leverage the combined power of Step and Cypress.
Installation The Cypress plugin is enabled by default for the Enterprise and SaaS versions of Step. To use the plugin you simply have to install Node.js on the Step Agents you&amp;rsquo;ll want to run Cypress Keywords on.</description>
    </item>
    
    <item>
      <title>Grafana k6 Plugin</title>
      <link>https://step.dev/knowledgebase/31/plugins/k6/</link>
      <pubDate>Wed, 10 Apr 2019 14:24:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/plugins/k6/</guid>
      <description>Grafana k6 is a powerful, open-source load testing tool developed by Grafana Labs. It is widely used for scripting and executing performance tests with high efficiency and developer-friendly ergonomics.
The k6 plugin for Step enables seamless integration of existing k6 scripts into the Step platform, unlocking a broader range of automation capabilities. This integration allows users to combine the strengths of both tools, leveraging k6’s expressive scripting model alongside Step’s orchestration, scheduling, and extensibility.</description>
    </item>
    
    <item>
      <title>Silk Performer Plugin</title>
      <link>https://step.dev/knowledgebase/31/plugins/silk-performer/</link>
      <pubDate>Wed, 10 Apr 2019 14:24:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/plugins/silk-performer/</guid>
      <description>Silk Performer is a load testing tool by openText.
Step can execute Silk Performer projects via a dedicated plugin available to Step enterprise customers. This page describes how to configure and use this plugins.
Installation Before using this plugin, the Complete Installation of Silk Performer has to be done on the machine running your agents.
Finally, you will specify the installation folder of Silk performer in the AgentConf.yaml of your agent:</description>
    </item>
    
    <item>
      <title>JMeter</title>
      <link>https://step.dev/knowledgebase/31/plugins/jmeter/</link>
      <pubDate>Wed, 10 Apr 2019 14:24:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/plugins/jmeter/</guid>
      <description>The JMeter integration plugin allows you to integrate existing JMeter tests into Step as Keywords, which can then be used in Plans like any other Keyword.
This means that you can use existing JMeter tests for massively parallel load test executions (distributed across multiple Agents), synthetic monitoring or any other disciple supported by Step.
It supports following features:
Passing of Keyword inputs to JMeter Passing of Parameters (properties) to JMeter Automatic generation of performance measurements based on the JMeter samples Attachment of the JMeter logs Installation On-premises installation The JMeter plugin is provided by default with Step Open source and Step Enterprise, but JMeter needs to be downloaded separately on the controller and the following option should be modified accordingly in the step.</description>
    </item>
    
    <item>
      <title>Advanced executions</title>
      <link>https://step.dev/knowledgebase/31/userdocs/executions/execution-advanced/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/userdocs/executions/execution-advanced/</guid>
      <description>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.</description>
    </item>
    
    <item>
      <title>A new blog entry for browser-based load-testing with step</title>
      <link>https://step.dev/knowledgebase/31/whatsnew/news/browser-based-load-testing-blog/</link>
      <pubDate>Fri, 11 Feb 2022 11:39:07 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/whatsnew/news/browser-based-load-testing-blog/</guid>
      <description>Over the past few years, many tools have sprung out trying to address the requirements of Load-testing. They have all aimed at making the life of testers easier and giving the business the necessary insights on the performance of their code. Of the many load-testing offerings, Browser-based Load-testing solutions have picked up pace in the recent past.
Benefits of browser-based load-testingJust click the button above to access blog.</description>
    </item>
    
    <item>
      <title>New White Paper: the TCO of browser automation</title>
      <link>https://step.dev/knowledgebase/31/whatsnew/news/new-whitepaper-selenium/</link>
      <pubDate>Thu, 11 Jul 2019 08:11:28 +4400</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/whatsnew/news/new-whitepaper-selenium/</guid>
      <description>We&amp;rsquo;ve just published a new white paper covering the pitfalls of legacy HTTP solutions in the world of testing and addressing the need for information on newer alternatives in the open-source scene such as Selenium or Pupeteer. We&amp;rsquo;ll also see how easy and cheap it is to scale the execution of tests using these new libraries on top of step&amp;rsquo;s agent grid, and in particular, in the cloud.
Take me to the White PaperJust click the button above to access the white paper.</description>
    </item>
    
  </channel>
</rss>
