Getting Started

Testerum is not only a tool to define automated tests but also a tool to document your project. We can achieve this by allowing you to define and describe your project functionalities (features). The behavior of each feature can be described using Acceptance Criteria in a Behavior Driven Development (BDD) way. Each Acceptance Criteria can be used as a Manual Test or can be transformed into an Automated Test.

How to create a Feature

First of all we need to create a new Project or to open an existing one
On the Home Page click Create New Project button or Open Project button
Hover your mouse over "YourProjectName" or over an existing feature and you will see that a context menu button appears. (img 1)

img 1
On the right side of the screen will appear a window Create SubFeature (img 2). Here you will be able to:

Provide a Name for your Feature (mandatory)
You can provide a list of tags. This tags can be used for filtering and reports
Create a description of your feature. Testerum uses markdown for text formatting. Find more details about markdown formatting here.
Add attachments.

img 2

Tip: A good description will help your team fully comprehend your feature. The behavior of your feature will be described using Acceptance Criteria.

How to create Acceptance Criteria (Manual Test)

Each feature has a set of acceptance criteria which describes the product’s expected behaviour.
The acceptance criteria will immediately serve as manual tests. Let’s see how it’s done:

Navigate to your Feature tree.
Hover over your newly created Feature and press Create Test button. This is the Plus button.(img 3)

img 3
On the right side of the screen will appear a window Create Test (img 4). Here you will be able to:

Name your test. Additionally, you can add a description and tags.
In Type category you can define if is a Manual or Automated test and if is Enabled or Disabled. For now let's define the test as Manual.
You can provide a list of tags. These tags can be used for filtering and reports
You can add a Description. Testerum uses markdown for text formatting. Find more details about markdown formatting here.

img 4

Now click on Plus button next to Steps in order to define the Acceptance Criteria Steps (img 5).

Acceptance Criteria Steps should reflect the business language and written in a Behaviour Driven Development (BDD) style.
Each step should start with Given, When or Then word.
Attention! If the steps you are defining are red is because you haven't marked the test as manual.
In the section How to transform a Manual Test in to an Automated Test we show you how to implement these steps as automated steps

img 5

After you're done adding your steps, save the test.

How to transform a Manual Test into an Automated Test

Given you have a manual test defined

First, you need to mark the test as Automated (img 6)
All the steps will be red. This is because the behavior of the steps is not implemented.
To implement the step behavior click on the step to see the "Sub-Steps" node.
Hover the mouse over the "Sub-Steps" node and click the + (Add Sub Step) button

img 6

Now, an input box was added as a Sub Step.(img 7)
In here, if you know the name of the sub-step that you need to implement the parent behavior you can type the keyword to get the suggestions.
If you don't, press the + button to select the step from the Step Chooser pop-up screen

img 7

In the Step Chooser there are two main steps categories: (img 8)
- Composed Steps are the steps defined by you that reflect your business needs
- Basic Steps are predefined steps that allow you to interact with different technologies.
  Using these steps you can:
  - interact with a browser using the Selenium integration
  - make and verify HTTP calls
  - initialize and verify databases
  - mock 3rd Party APIs
  - etc.
Choose the steps that you need to implement the action you want and press the Add Step button.

img 8

After you're done adding your steps, save the test.