[MGNLMIGRATION-216] Define integration tests in order to preserve the consistency between the configuration of a migrated magnolia module and a freshly installed one Created: 21/Jan/13  Updated: 25/Apr/14  Resolved: 15/Mar/13

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2.2-beta1, 1.2.2

Type: Task Priority: Blocker
Reporter: Samuel Schmitt Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLMIGRATION-319 Migration project could depend on low... Closed
dependency
depends upon MSHOP-57 The configuration of SHOP between a n... Closed
depends upon MGNLCMNT-73 The configuration of Commenting betwe... Closed
depends upon MGNLCMNT-86 CLONE - The configuration of Commenti... Closed
depends upon MGNLPUR-80 The configuration of PUR between a ne... Closed
depends upon MGNLSTK-1073 The configuration of STK between a ne... Closed
depends upon MGNLSTK-1076 Add conditionList areas placeholders,... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

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.



 Comments   
Comment by Samuel Schmitt [ 21/Jan/13 ]

I set it on blocker because before being able to proceed with the following tickets: MGNLFORM-148, MGNLSTK-1073, MGNLPUR-80, MGNLCMNT-73, MSHOP-59, the integration test must be done.

Comment by Robert Šiška [ 15/Mar/13 ]

We need to remove non-existing classes from config repository to prevent ClassNotFoundExceptions.

Generated at Mon Feb 12 10:18:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.