Examine JUnit test cases for migration needs prior to launching them
The migration service is not applied to models that are programmatically loaded. Instead, it is launched when projects are discovered in the runtime workspace. This applies to existing models and imported ones that are copied to this workspace.
Add an extra utility method for model loading from test cases. It shall check whether migration is needed and fail the test if a model update is needed. These updates can only be done manually, so it is better to fail early than failing test cases when a model migrator is removed.
#2 Updated by Alexander Diewald 3 months ago
- Status changed from New to Resolved
- Assignee changed from Alexander Diewald to Tiziano Munaro
- % Done changed from 0 to 100
This one overlaps with the refactoring done in #3993.
If you have too much to do, please reassign to me :)
For testing, revert the test model update of StateAutomataConstraintsCheckerTestData and execute the lauch cfg "AllTests". One of it should fail, asking for manual model migration.