Skip to main content

Know when to adapt to next revision

Explanation

Test Configurations are always built upon a single currently loaded Application Revision. The information in that revision is used to determine which objects and object values can exist in the database, and which microflows can be executed. This in turn allows to create the necessary Teststeps that are needed to build a test in MTA. And, when the test is executed, gives some guarantee that these model elements also exist in the Application Instance that the test is running on.

To allow Test Configurations to stay updated with changes done in the Mendix model, they can be adapted to another revision. Note that this does not necessarily have to be a newer revision, it can be any revision on any branch of the App. Downloading a revision can be done in the background by using a Branch Subscription, but adapting must be done manually because adapting can lead to Construction Errors.

Construction Errors in a Test Configuration will block executing it. Executing would lead to an error in the Test Run, because model elements don't match. But, it is not always necessary to adapt to the revision of the Application Instance, in order to Execute the Test Configuration. Below is a list of scenario's, which would lead to an error when executing or not.

Scenario

info

Microflow means any Microflow or Rule
Used? means the entity, attribute or microflow is used in a teststep

Change done in next revisionIs Used?Result after adaptExecute without adapt
Added entityN/A
Deleted existing entityNot Used
Deleted existing entityUsed in TeststepConstruction ErrorRuntime Error
Added attributeN/A
Deleted existing attributeNot Used
Deleted existing attributeUsed in TeststepConstruction ErrorRuntime Error
Added associationN/A
Deleted existing associationNot Used
Deleted existing associationUsed in TeststepConstruction ErrorRuntime Error
Renamed entityNot Used
Renamed entityUsed in Teststep
Renamed attributeNot Used
Renamed attributeUsed in Teststep
Renamed associationNot Used
Renamed associationUsed in Teststep
Other domain model changeNot Used
Other domain model changeUsed in Teststep
Added microflowN/A
Deleted existing microflowNot Used
Deleted existing microflowUsed in TeststepConstruction ErrorRuntime Error
Added input parameterNot Used
Added Primitive input parameterUsed in TeststepRuntime Error
Added Object input parameterUsed in TeststepConstruction ErrorRuntime Error
Deleted input parameterNot Used
Deleted input parameterUsed in TeststepConstruction ErrorRuntime Error
Changed parameter datatypeNot Used
Changed parameter datatype *Used in TeststepConstruction ErrorRuntime Error
Renamed input parameterNot Used
Renamed input parameterUsed in Teststep
Changed return valueNot Used
Changed return valueUsed in TeststepConstruction ErrorRuntime Error
Other microflow changeNot Used
Other microflow changeUsed in Teststep
Any other model changeN/A

* Upon adapting, some primitive datatypes are convertable by MTA when they are changed, and will not lead to a Construction Error.

For more information, also see the Using Primitives chapter in "Use previous teststeps data".

Feedback?

Missing anything? Let us know!

Last updated 16 July 2025