As a Product Owner, you can document the product’s vision and share it with the team using our ‘Features’ functionality.

In Testerum, one feature can contain a tree of sub-features.

Acceptance Criteria

Basically every functionality has a list of Acceptance Criteria which defines details of the expected behavior.

Notice that Acceptance Criteria are written in the business language.

Acceptance Criteria are initially manual tests but can be transformed into automated tests.

Acceptance Criteria As Automated Test

Any Acceptance Criteria can easily be converted into an Automated Test simply by selecting corresponding ‘Basic Steps’ (multiple integrated technologies) or by creating your own ‘Composed Steps’ (check below) from a selection of Basic Steps.

Basic Steps

By calling ‘Basic Steps’ you can easily transform any Acceptance Criteria into Automated Tests.

‘Basic Steps’ are a result of our integrations with multiple technologies such as Selenium, Http, different Databases, mocking 3rd party APIs and many more.

Testerum comes with built-in comprehensive Basic Steps for the most common technologies, but you can always write new basic steps which suit your needs.


Selenium Basic Steps allow you to automate web application testing. It supports many browsers such as Firefox, Chrome, IE, and Safari. And if you want to run these tests on your CI server, you can use the headless mode of Chrome or Firefox.

HTTP Request

Using this Basic Step you can make as many HTTP Requests to the API as you want to test.

HTTP Response Verify

And to be sure that everything works as expected, with this step, ‘HTTP response’, you can verify the result.


In order to isolate your application from 3th party services you need to simulate their API.

This Basic Step starts an HTTP server that matches incoming requests against previously configured expectations. An expectation defines the action that is taken, for example, what HTTP response should be returned.

Also, this step allows you to test your web or mobile frontend module without the server part.

Relational Database Initialize

This basic steps authorizes you to execute SQL scripts against a specific relational database.

Relational Database Verify

During some actions in your application the data in the database might change. This step permits you to easily check that the current state of the database it is as you expect it to be.

Composed Steps

A Step is a line of text which represents an action in Acceptance Criteria.

Any action you define in Acceptance Criteria can be divided in multiple sub-actions. A Composed Step translates the business language into one or more technical actions (Basic Steps).

The last step of the sub-steps tree must be a basic action (a technology integration step).

Automated Tests Results

See at a glance the state of your system.

Manual Tests

Any Acceptance Criteria, unless transformed into Automated Tests can be used as Manual Tests.

Manual Test Plan

On each release or iteration you can create a Manual Test Plan to check the quality of your software. A Manual Test Plan is a collection of Manual Tests that needs to be executed at a certain moment.

Manual Test Plan Execution