Uploaded image for project: 'Migration 4.4 to 4.5 (closed)'
  1. Migration 4.4 to 4.5 (closed)
  2. MGNLMIGRATION-216

Define integration tests in order to preserve the consistency between the configuration of a migrated magnolia module and a freshly installed one

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • 1.2.2-beta1, 1.2.2
    • None
    • None
    • None

      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.

        Acceptance criteria

              rsiska Robert Šiška
              sschmitt Samuel Schmitt
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Task DoR