Skip to main content
Version: 3.1

Teststep

Definition​

A Teststep tests some specific aspect of system behaviour. A Teststep is always part of a Test Case.

The Teststep is the lowest or fourth level of the 4-layer framework that is used in MTA. It describes the actual operating functions.

A Teststep must be one of the following types:

An Object Teststep can execute the following actions:

  • Create: create an object (without committing it to the database).
  • Retrieve: retrieve object(s) from memory or database.
  • Change: change an object (without committing it to the database).
  • Delete: mark an object to be deleted. When deleting, always make sure to have the Delete teststeps in the right order, to make sure domain model Delete Constraints don't prevent deletion of the object(s).
  • Persist: finalizes above Object teststeps.

Note that if a retrieved object is deleted by a Delete Object Teststep in MTA, and afterwards changed in another Teststep, MTA will not give a warning during test design, but give a runtime error on test execution because the object to be changed is no longer available.

Properties​

Name​

The name of the Teststep. Edit the teststep to change.

Description​

A description of the Teststep. Edit the teststep to change.

Execution condition​

SettingResult
NoneThe Teststep will be part of the Test Run if the parent Test Case, Test Suite or Test Configuration, is executed, and does not stop due to an Exception. The Teststep will NOT be part of the Test Run if the parent Test Suite or Test Case has the Execution condition = Skip setting.
SkipThe Teststep will NOT be part of the Test Run if the parent Test Case, Test Suite or Test Configuration, is executed.
AlwaysThe Teststep will be part of the Test Run if the parent Test Case, Test Suite or Test Configuration, is executed, even if a previous Teststep encounters an Exception. The Teststep will NOT be part of the Test Run if the parent Test Case or Test Suite has the Execution condition = Skip setting.

Exception handling​

Determines if the Test Run will either Continue, or Stop, if a Teststep Exception occurs in this Teststep, that is not handled by a Mendix Error Handler.

Delay after execution​

Delays the execution of this teststep with specified milliseconds. Edit the teststep to change.

Highlight​

Highlights the Teststep yellow in the list, to draw attention to it. Edit the teststep to change.

Category​

Can be either 'Object' or 'Microflow'.

Action​

Only for Object Teststeps; either 'Create', 'Retrieve', 'Change', 'Delete' or 'Persist'.

Retrieve set​

Only for Retrieve Object Teststeps; either 'All objects', or 'Only First object'.

Retrieve option​

Only for Retrieve Object Teststeps; either 'From database', 'From former Teststep', or 'By association' (from memory).

Microflow Name​

Only for Microflow Teststeps; Name of the microflow to be executed.

Business rules​

  • The name is mandatory.
  • A Microflow Teststep must have a microflow selected in order to be able to execute the Test Configuration.
  • An 'Create', 'Change' or 'Retrieve' Object Teststep must have an entity selected in order to be able to execute the Test Configuration.
  • It is not allowed to select the Execution condition = Skip setting on a Teststep that provides data to another Teststep.

Actions on Teststep​

View Teststeps in a Test Case​

  • Navigate to the Test Suite that the Teststeps are in.
  • Expand the Test Case to view the Teststeps.
  • Properties are shown on the right.

View Teststep Dependencies​

  • Select the Teststep to view Dependencies.
  • If there are Teststep(s) above, that this Teststep depends on, there is a Receiving indicator. Clicking on it will allow to navigate to those Teststep(s).
  • If there are Teststep(s) below, that depend on this Teststep, there is a Providing indicator. Clicking on it will allow to navigate to those Teststep(s).

Create a Teststep​

Move a Teststep​

Move a teststep 1 position up or down.​

  • Click on the button on the Teststep.
  • Click on or "" to move the Teststep up or down.
  • Review and Construction Errors.

Move Teststeps inside a Test Case.​

  • Click on the button on the Teststep or Test Case.
  • Click on Arrange Teststeps.
  • Review any Construction Errors.

Move a Teststep to another Test Case.​

Edit a Teststep​

  • Select the Teststep.
  • Make the changes in the Teststep details, shown on the right.

Note that it not is possible to change the action or type of Teststep after creation, or change the entity or microflow that it is associated with.

Configure a Teststep​

  • Click on on the Teststep name to set the Attribute Values or Microflow Parameter Values.

When setting Attribute Values, always keep in mind that the meaning of the value is different for a Retrieve action.

  • For Create / Change Object actions and Microflow parameters, the Attribute will be assigned the entered value, and 'empty' if checked, but left blank.
  • For a Retrieve Object action, the resulting set of objects will be filtered by the entered value, and 'empty' if checked, but left blank.

Note that it not is possible to change the action or type of Teststep after creation, or change the entity or microflow that it is associated with.

Delete a Teststep​

  • Navigate to the Test Case that the Teststep is in.
  • Click on the button on the Teststep.
  • Click on Delete.

Note that it is possible that due to deleting a Teststep and dependencies with another Teststep, a Construction Error will occur prohibiting the execution of the Test Configuration.

Feedback?​

Missing anything? Let us know!

Last updated 26 May 2026