Sample projects for Step — the open-source open-source automation platform that unifies software automation across the entire DevOps lifecycle.
The automation-packages directory is the primary entry point for this repository. It contains ready-to-run samples covering the most common automation use cases, each structured as a self-contained Step Automation Package.
What is an Automation Package?
An Automation Package is a single deployable artifact (JAR, zip, or folder) that bundles keywords, plans, schedules, and parameters together. It is the recommended way to organize and deploy automation with Step.
Browse the automation-packages/README.md for a full index of samples with filtering by use-case, framework, language, and complexity level.
| Use case | Examples |
|---|---|
| Load testing | Playwright, Selenium, Cypress, JMeter, k6, OkHttp, gRPC, Appium, Serenity BDD |
| E2E testing | Playwright (Java, TypeScript, JavaScript), data-driven, shared library |
| Monitoring | Synthetic monitoring with Playwright and Cypress, advanced alerting |
| RPA | Selenium-based back-office automation with CSV data sources |
These directories contain older, lower-level samples that predate Automation Packages. They remain useful as reference material for individual keywords or Step client usage.
| Directory | Contents |
|---|---|
| keywords | Standalone keyword examples by technology (Java, .NET, Cypress, TypeScript/Playwright, JMeter, k6, Oryon, gRPC, SoapUI, …) |
| plans | Example Step plan files (JSON and YAML) |
| step-client | Sample projects using the Step Controller API (Java and REST) |
| plugins | Example Step plugin |
| maven-plugins | Sample for the Step Maven upload plugin |
Samples of open-source features rely exclusively on public dependencies and build without any specific prerequisites.
Enterprise samples require a Step Enterprise license and depend on artifacts hosted on the exense private Nexus. Add the following to your ~/.m2/settings.xml:
<servers>
<server>
<id>nexus-exense</id>
<username>your_step_enterprise_username</username>
<password>your_password</password>
</server>
</servers>If your environment uses an HTTP proxy:
<proxies>
<proxy>
<id>step-proxy</id>
<active>true</active>
<protocol>http</protocol>
<host>your_proxy</host>
<port>your_proxy_port</port>
<nonProxyHosts>*.yourdomain</nonProxyHosts>
</proxy>
</proxies>The quickest way to get started is stepcloud.ch — create a free account, get evaluation credits, and have a fully managed Step instance running in minutes with no infrastructure to set up. This is the recommended approach for trying out these samples.
For an on-premise installation, download the latest release from github.com/exense/step/releases and follow the installation guide.
- Documentation: step.dev
- Support: step.dev/contact