-
Task
-
Resolution: Fixed
-
Blocker
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Since the issue MGNLSTK-1073 identified, we decided that we need tests that guarantee the configuration of a migrated module and of a new installation is the same.
What the tests must do:
- run the latest version of the migration on a module
- compare this configuration with a freshly installed module
- the test are ok only if the configuration is the same
The affected modules are: STK, FORM, SHOP, PUR, Commenting.
To run the tests, build with integration-test profile:
$ mvn install -P integration-test
Details of tests:
Jetty container with two web applications is run. One is magnolia-migration-webapp, which contains old repository
and migrates after start. The second one is magnolia-migration-freshapp, which contains freshly installed modules.
magnolia-migration-tests installs new servlet ExportServlet to both instances.
This servlet is called by tests from magnolia-migration-integration: they use ExportServlet to export individual modules
from both instances and compare them.
- depends upon
-
MSHOP-57 The configuration of SHOP between a new instance and a migrated instance must be the same
- Closed
-
MGNLCMNT-73 The configuration of Commenting between a new instance and a migrated instance must be the same
- Closed
-
MGNLCMNT-86 CLONE - The configuration of Commenting between a new instance and a migrated instance must be the same
- Closed
-
MGNLPUR-80 The configuration of PUR between a new instance and a migrated instance must be the same
- Closed
-
MGNLSTK-1073 The configuration of STK between a new instance and a migrated instance must be the same (part 1)
- Closed
-
MGNLSTK-1076 Add conditionList areas placeholders, Update editor used on profile-update page
- Closed
- is causing
-
MGNLMIGRATION-319 Migration project could depend on lower versions
- Closed