Skip to main content
Version: 2.10

Delete Object

Definition​

With this Teststep type, an object or objects from a previous Teststep is marked for deletion.

To delete it from the database, add a Persist step.

Domain model Access​

Domain model access rights apply if the Test Case that the teststep is in, has Apply Security enabled.

Upon executing a Delete teststep, MTA will evaluate the Execution user's Delete rights on the Domain Model through the configured User Roles.

If the necessary rights are not found in the Domain Model, an error will be shown on the Test Run, and the Test Run will stop.

To circumvent domain model access rights it is possible to use a Microflow teststep.

Actions​

Add a Delete Object Teststep​

There are two options to Delete an Object. The first option is quicker:

Option 1:

  • Click on the '' button on the Teststep that returns the object that you want to delete, and choose " Delete output".

Option 2:

  1. Select the Test Case that you want to create a Teststep in.
  2. Click " Add" and Click " Delete teststep" to add a Delete Object Teststep.
  3. Select an entity. You can search by name.
  4. Select the previous Teststep that returns the object that needs to be deleted. This could be a Create, Change or Retrieve Teststep but also a Microflow Teststep that returns an object.
  5. Click on the "Save" button.

When deleting objects from multiple entities, 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).

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.