Overview

• ability to use debugger against test webapp (IDE integration, problematic with Docker!), maybe research remote debugging possibilities with Dockerised webapp.
• restore the ability to run the tests against the local instance with some "hot" changes.
• cosider the possibility of the VM-based test execution (optionally)
• consider setup configuration additions that would let the user execute the tests in a way they want

Issues with the "fully local setup"

In the fully local setup you run all the things directly on your laptop, neither using docker nor a virtualbox.

For this scenario, when running test based on the "old" ui-test-framework, it was required to apply a patch (adapting info.magnolia.integrationtests.docker.IntegrationTestEnvironment and info.magnolia.integrationtests.rules.SeleniumNodesVncSidekickRule), see no_docker_patch.txt.

UI tests utilizing the new UI-test-framework which uses JUnit-5  in this setup now fail with throwing a RuntimeExc. in info.magnolia.testframework.VncRecordingHelper. See stacktrace.

It should be possible to run also the new ui-tests "fully local". Ideally we can find a solution which doesn't require a patch.

Making the patch into the codebase will fix the issue for the non-docker setup but will break the case when dockerised setup is deployed manually and is not required to be provisioned by the integration tests. However, 
verifying the presence of the server }}container and ensuring that{{ localhost:8599 leads to its *:8080 port should be a reliable sign that we’re using the dockerised setup.
If container is not up or ports are configured to use some other instance - we’re clearly by-passing the thing.