[MGNLTEST-49] Enable running of JUnit5 and JUnit4 UI tests on Jenkins Created: 26/Sep/19  Updated: 09/Oct/20  Resolved: 20/Jan/20

Status: Closed
Project: Magnolia Test Framework
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Federico Grilli Assignee: Maxime Michel
Resolution: Done Votes: 0
Labels: junit5
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLCE-178 Adapt CE's Maven profiles to the new ... Accepted
relation
is related to MGNLTEST-51 Complete phase 1 of new page object b... Closed
is related to MGNLTEST-52 Provide self-tests for high-order pag... Closed
is related to MGNLTEST-31 Enable parallel execution of JUnit 5 ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: core-TF-features-bugs-improvements
Sprint: now
Story Points: 3

 Description   

Follow-up to MGNLCE-166

An attempt was already made at configuring maven-surefire and maven-failsafe plugins to run both the new Jupiter/JUnit5 based UI tests and the legacy ones written with JUnit4, see https://git.magnolia-cms.com/projects/PLATFORM/repos/ce/commits/d576be85fe9e3da1b99f6d9cabfd0e3d2a3b95ea

However, that apparently resulted in breaking the configuration for running UI tests in parallel which passed from ~12' to ~40' to complete.   
The behavior for concurrent execution of UI tests is orchestrated by the UI test pipeline and executed via failsafe plugin config at https://git.magnolia-cms.com/projects/PLATFORM/repos/ce/browse/magnolia-integration-tests/tests/pom.xml#357

Maven upgrade

As the following page indicates, Maven 3.6+ is needed for JUnit5 support without an additional Maven plugin. This is why we are bumping the version used by Jenkins for 3.5.2 to 3.6.2.



 Comments   
Comment by Maxime Michel [ 15/Oct/19 ]

Relevant link: https://maven.apache.org/surefire/maven-failsafe-plugin/examples/junit-platform.html

Comment by Maxime Michel [ 15/Jan/20 ]

This ticket is now about running the fairly dirty approach of tweaking the POM file on Jenkins. The goal is to get tests running, and to improve the JUnit 4/5 situation later on, as a ton of time was dedicated to that, but without any clear success yet.

Generated at Mon Feb 12 07:45:04 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.