Automation as Code
Step’s unique Software automation as Code (short Automation as code) approach enables developers to define software automation workflows for the whole DevOps lifecycle as code alongside the actual application’s code.
Read More »
Automation Packages
Based on the Automation as Code paradigm, the new Automation Package extends Step with DevOps-native functionality, allowing to maintain application and automation code in tandem, and bringing powerful automation capabilities to DevOps pipelines, as well as simplifying Step’s own usage and maintenance.
Read More »
Dev Overview
Get to know how to develop keywords what APIs are made available to you.
Read More »
Automation Package descriptor
Automation Packages Definition format
Read More »
Maven plugin
The Step Maven plugin serves as Command Line Interface (CLI) for all operations related to Automation Packages. It provides an integration with the Step server and an easy way to integrate Step with a CI/CD pipeline.
Read More »
Keyword API
Using the Keyword API.
Read More »
Step CLI
The Step CLI is a Command Line Interface for all operations related to Automation Packages available for Windows and Unix System. It provides an integration with the Step server and an easy way to integrate Step with a CI/CD pipeline.
Read More »
Automation Package in Java
Automation Packages Definition in Java code
Read More »
Step client API
The Step client exposes means to connect to the controller programmatically, access and use Step services in a headless way via the class STEPClient.
Read More »
REST API
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.
Read More »
Event Broker API
The Step client exposes means to connect to the controller programmatically, access and use Step services in a headless way via the class STEPClient.
Read More »
Automation Package CLI
Automation Packages come with a full-featured CLI that allows to build, execute and deploy Automation Packages
Read More »
DevOps
DevOps
Read More »