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
Microflow means any Microflow or Rule
Used? means the entity, attribute or microflow is used in a teststep
| Change done in next revision | Used? | Executing when not adapting to next revision |
|---|---|---|
| Added entity | N/A | |
| Deleted existing entity | No | |
| Deleted existing entity | Yes | Error |
| Added attribute | N/A | |
| Deleted existing attribute | No | |
| Deleted existing attribute | Yes | Error |
| Added association | N/A | |
| Deleted existing association | No | |
| Deleted existing association | Yes | Error |
| Renamed entity | No | |
| Renamed entity | Yes | |
| Renamed attribute | No | |
| Renamed attribute | Yes | |
| Renamed association | No | |
| Renamed association | Yes | |
| Other domain model change | No | |
| Other domain model change | Yes | |
| Added microflow | N/A | |
| Deleted existing microflow | No | |
| Deleted existing microflow | Yes | Error |
| Added microflow input parameter | No | |
| Added microflow input parameter | Yes | Error |
| Deleted microflow input parameter | No | |
| Deleted microflow input parameter | Yes | Error |
| Renamed microflow input parameter | No | |
| Renamed microflow input parameter | Yes | |
| Changed microflow return value | No | |
| Changed microflow return value | Yes | Error |
| Other microflow change | No | |
| Other microflow change | Yes | |
| Any other model change | N/A |
Feedback?
Missing anything? Let us know!
Last updated 23 October 2024