Step is a comprehensive solution designed to allow testers and developers to work together efficiently and to focus on what they're best at. The content of that solution is two-fold:

  • a platform comprising multiple software components:
    • a scalable agent grid to run test code in parallel
    • a mongodb database instance used to persist test artefacts and execution results
    • a central controller which orchestrates test executions and provides access to a web application allowing users to design their tests and analyze their results
  • a framework which provides developers and testers with various APIs and libraries:
    • the Keyword API, which aims at decoupling test case implementation from its specification and data (inputs, outputs, expected results)
    • a set of other APIs allowing developers to extend other areas of the product (such as interoperability APIs, customized reporting, etc)
    • prepackaged dependencies and libraries which allow developers to get started quickly started on common use cases such as Selenium/WebDriver scripting, JMeter or Grinder integration
    • a library of test artefacts and packages which offer a wide range of services frequently used in a testing context (i.e reading and writing data from/to Excel, SQL or other datasources, load semantics such as threads, iterations and pacing, automatic error handling, etc)
    • as we accumulate experience, we're also building and maintaining a library of concrete examples based on work we've done on the battlefield

The STEP Platform

Here's a quick glance at what STEP's architecture looks likes:

step architecture.PNG

The STEP Framework

Here's the main idea behind the Keyword API and what it looks like when working in Java or .NET (our two most dominant platforms):


Other APIs allow integration with different libraries, testing tools, data repositories, etc:


Where to start

To get a first feel of what STEP does, you can start with our installation steps here.

Once you've installed a local instance, you can start playing around with the demo keywords that are preconfigured and create your first test plan.

You can then move on to creating your first keyword, starting a Selenium project and deploying it on the platform. We've documented most of that in our development section here.

Finally, you can browse the rest of the documentation to learn about more advanced uses of the built-in test plan features, find other examples, learn how to operate your platform or how to use some of our many plugins by browsing the corresponding documentation pages. You'll find most of what you need by navigating the left menu of this webpage.

Created by Jerome Brongniart on 2019/03/11 13:43
Copyright © exense GmbH