Currently the test framework utilizes the moduleUiTestsPipeline to run UI tests on Jenkins on a single magnolia instance. The average build times for PRs are now approaching 20 minutes, with more POs in the queue to be added.

• Consider adding configurable parameters to the Jenkins pipeline to enable multi instance setup to speed up the builds.
• This will also require enabling the forked VM setup for test framework (for which a parent pom should be updated)
• Selenium standalone needs to be dropped from docker-compose in favor of selenium hub + node setup (with port range mappings for exposed ports on both magnolia and selenium node containers)

Implementation notes

• replicate IT setup from non-TF pipelines
• possible Failsafe / JUnit5 issue to enable parallelism?