https://step.dev/knowledgebase/31/categories/getting-started/ Recent content in Getting Started on Step Documentation Hugo -- gohugo.io en Mon, 08 Jun 2026 00:00:00 +0000 https://step.dev/knowledgebase/31/setup/download/ Wed, 25 Sep 2024 00:00:00 +0000 https://step.dev/knowledgebase/31/setup/download/ This page provides an overview of the available downloads for the various Step components. Step CLI The Step CLI (Command Line Interface) provides an interface for building, executing, and deploying automation packages within Step. CLI for Step Open Source The CLI of Step Open Source can be downloaded from the GitHub releases page of Step. Following binaries are available, depending on your platform: Windows: step.exe Linux and Mac: step After download, put the executable corresponding to your platform in your PATH. https://step.dev/knowledgebase/31/saasdocs/quick-setup-saas/ Thu, 25 Jan 2024 09:52:31 +0100 https://step.dev/knowledgebase/31/saasdocs/quick-setup-saas/ This guide helps you get your first Step SaaS cluster up and running in a few simple steps. Afterward, you can explore our tutorials to create and deploy your first distributed workflows, on the newly created cluster. Step SaaS offers an evaluation plan to easily get started and follow our tutorials. Step 1: Sign up for the Step portal Sign up for the Step portal here. Use your full name also in the Organization field if you do not represent an organization. https://step.dev/knowledgebase/31/setup/requirements/ Mon, 29 Nov 2021 14:08:01 +0100 https://step.dev/knowledgebase/31/setup/requirements/ On-premise requirements Below is a list of minimal hardware, system, and software requirements to set up Step. The specified versions of third-party software correspond to the ones officially tested and supported. Step Controller Step DB per Step Agent OS Redhat, SLES, Debian, Windows 7 to 10, Windows Server 2012 to 2022 Redhat, SLES, Debian, Windows 7 to 10, Windows Server 2012 to 2022 Redhat, SLES, Debian, Windows 7 to 10, Windows Server 2012 to 2022 Software: Oracle/Hotspot JDK 21 to 25 installed MongoDB 5. https://step.dev/knowledgebase/31/userdocs/keywords/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/keywords/ This section explains how to register and use existing Keywords. To learn how to develop custom keywords, check the Developer guide overview. What is a Keyword? Keywords are the fundamental building blocks of Plans. They encapsulate automation logic, often referred to as scripts. A Keyword can represent a fully automated flow or a more granular action, such as a user interaction or an API call. In general, finer-grained Keywords are preferred because they are easier to reuse across multiple business flows through Plans. https://step.dev/knowledgebase/31/setup/installation/binaries/quick-setup/ Wed, 13 Feb 2019 12:52:31 +0100 https://step.dev/knowledgebase/31/setup/installation/binaries/quick-setup/ The goal of this guide is to get your first Step cluster running in minutes. After this you can follow our additional tutorials to learn how to create and deploy your first distributed automation scripts (called “Keywords”) on this freshly created cluster. Step SaaS and Step on-prem Step is available in different versions as described in Step pricing. Since we already prepared everything for you in the full-serviced SaaS solution, the easiest way to start using Step is to follow the Getting started with Step SaaS. https://step.dev/knowledgebase/31/ai/mcp-server/getting-started/ Mon, 08 Jun 2026 00:00:00 +0000 https://step.dev/knowledgebase/31/ai/mcp-server/getting-started/ Overview The Step MCP Server lets AI assistants and coding agents (such as Claude Code, Claude Desktop, and Cursor) drive the Step automation platform through the Model Context Protocol (MCP). It brings AI-powered software testing into your existing automation workflows: agents can author, run, and analyse test executions on Step without leaving their environment. Instead of clicking through the UI, you can triage a failed run (even a load test with thousands of failures) by asking in plain language and getting a cited root-cause summary back. https://step.dev/knowledgebase/31/devops/automation-packages-overview/ Wed, 22 May 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/devops/automation-packages-overview/ The concept of Automation Packages provides a standard for defining software automation workflows for the whole DevOps lifecycle in a unified way. Following the Automation as Code paradigm, it allows developers to define software automation logic as code alongside the actual application’s code, and provide all the means to execute and deploy this logic at the different stages of the DevOps lifecyle. Technically the Automation Package standard consist of: The Automation Package syntax that defines a standard to describe a wide range of automation workflows in a unified way The Automation Package format that defines a standard for packaging entities (like Keywords, Plans, Resources, data, etc) The Automation Package CLI that allows to build, execute and deploy Automation Packages Automation Packages in a nutshell In a nutshell an Automation Package is a self-contained set of Plans and their related entities (Keywords, Parameters, Resources…) that can be executed on a Step controller or deployed to it for later use. https://step.dev/knowledgebase/31/devdocs/dev_overview/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/devdocs/dev_overview/ In these sections, you’ll get to know how to develop Keywords, as well as how to extend and customize Step using our APIs. API Description and links Keyword Development Before jumping into the Keyword API details, get to understand the concept of keyword development Keyword API To develop keywords you should refer to our Keyword API page and may follow our tutorials Automation as code Automation as code enables developers to define software automation workflows for the whole DevOps lifecycle as code. https://step.dev/knowledgebase/31/userdocs/plans/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/31/userdocs/plans/ A Plan in Step is the implementation of an automation scenario such as a functional test case, a load test, an RPA routine, or a synthetic monitoring probe. Plans combine building blocks called Keywords with various controls that build up the execution logic of the automation scenario. As a beginner, make sure to understand the key concepts explained in the following sections before creating your first Plan. You will also find various ways to create different types of Plans in our tutorials. https://step.dev/knowledgebase/31/devops/devops-getting-started/ Tue, 06 Feb 2024 00:08:01 +0100 https://step.dev/knowledgebase/31/devops/devops-getting-started/ The easiest way to get started with Automation Packages is to use one of our tutorial projects. Load and performance tests For automated and continuous performances tests, the tutorials include a complete project definition with a few simple keywords and plans defining a short load test scenario. It should be straightforward to execute these projects and start from there by modifying them according to your needs. Browser-based load testing with Playwright Protocol-based load testing with okhttp Continuous load testing with Grafana K6 Synthetic Monitoring Similarly to the load and performance test scenario, the tutorial for synthetic monitoring contains simple keywords, execution plan and schedule to set up the synthetic monitoring. https://step.dev/knowledgebase/31/setup/ Tue, 30 Jul 2024 00:00:00 +0000 https://step.dev/knowledgebase/31/setup/ This section includes information on how to set up Step and get it running. https://step.dev/knowledgebase/31/saasdocs/ Thu, 25 Jan 2024 00:00:00 +0000 https://step.dev/knowledgebase/31/saasdocs/ This space is dedicated to the administration and operations of Step SaaS. https://step.dev/knowledgebase/31/whatsnew/news/knowledge-base-release/ Fri, 10 May 2019 14:24:01 +0100 https://step.dev/knowledgebase/31/whatsnew/news/knowledge-base-release/ As promised in our roadmap for 2019, we’ve built and release a brand new website dedicated to hosting documentation contents and various resources for on-boarding both technical and non-technical users interested in step. We’ve taken the opportunity to perform a massive overhaul of both the structure, the looks and the content of our documentation pages. We hope you’ll benefit from it and find the new site useful. Other than the traditional documentation pages, you’ll also find hands-on tutorials, case studies and white papers. 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 https://step.dev/knowledgebase/31/documentation/ Mon, 04 Feb 2019 00:00:00 +0000 https://step.dev/knowledgebase/31/documentation/ What is Step? Step is a full-featured orchestration platform for software automation. It unifies the software automation disciplines and enables the reuse of automation artifacts through the whole DevOps lifecycle, from large scale test automation to load & performance tests, RPA and monitoring. It provides all the means to make the most of existing automation artefacts by enabling their reusability over different automation tasks and teams on one centralized platform, and thus reduce duplication of code, tools and resources over projects: One platform Step focuses on providing a unique platform for the orchestration of multi-purpose scalable automation scenarios while integrating existing automation tools (mainly test automation tools) and DevOps platforms: