Current situation

Currently both the test-frameworks as well as the tests are in the same (sub)module(s).

ce

info.magnolia.bundle.test:magnolia-integration-tests
=> contains tests and frameworks in these packages:

info.magnolia.integrationtests.*
Contains the "old framework" as well as "old" tests based on the old framework.

info.magnolia.testframework.*
Contains the "new framework" with its page objects and the "self-tests" (tests for testing the page objects)

info.magnolia.functionaltests.*
This package will contain the new functional tests (which will utilize the new framework)

dx-core

info.magnolia.dx.test:magnolia-dx-core-integration-tests
=> contains tests for dx-core features and a few utility classes.

Tasks

Create distinct (sub)modules for the test-framework(s)

ce

Create new (sub?)module e.g. info.magnolia.qa:magnolia-integration-testframework.
The artifact should contain the testframework classes:

• The complete info.magnolia.testframework.*
• Parts of info.magnolia.integrationtests.*

dx-core

IF we will create page objects specifically for dx-core features, we may want to have them in a distinct submodule,
e.g. info.magnolia.dx.qa:magnolia-dx-core-integration-testframework

Move Abstract test classes of magnolia-integration-tests-framework

The main purpose of magnolia-integration-tests-framework seems to be to facilitate and configure the test environment including docker.
However, it also includes the class info.magnolia.testframework.htmlunit.AbstractMagnoliaHtmlUnitTest, which ias a base class for ui-tests based on the [HtmlUnit test framework|ttp://htmlunit.sourceforge.net/].
Such class should go to the submodule hosting the testframework (the new module described above).

Please also check info.magnolia.integrationtests.InstanceAwareTestCase , info.magnolia.testframework.util.TestUtil#TestUtil and probably move.

Maybe even consider to completely get rid of the submodule magnolia-integration-tests-framework