[MGNLTEST-36] Junit5 UI tests are no longer discovered by surefire/failsafe Created: 31/Mar/20  Updated: 08/Jul/20  Resolved: 27/May/20

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

Type: Bug Priority: Major
Reporter: Federico Grilli Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: QA&Testing, hardening-fwk
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: core-TF-features-bugs-improvements
Story Points: 5

 Description   

JUnit5 UI tests stopped running on Jenkins somewhen shortly before 6.2 release, possibly following some library update or Maven plugin update in ppom 38 but I wasn’t able to pinpoint what caused it.

One lead was that Groovy library update and its support for JUnit5 may have pulled in JUnit5 engine in the cp thus causing troubles. Tried to exclude that but didn’t solve the issue https://git.magnolia-cms.com/projects/BUILD/repos/boms/commits/f4180bea948a802cd64e64b9befe4910157ad77c



 Comments   
Comment by Rishab Dhar [ 19/May/20 ]

TODO

Update the ui test setup documentation for triggering UI tests from CLI, when the issue gets resolved.

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