[MAGNOLIA-8265] Move JUnit 5 extensions and related testing utilities to a dedicated module Created: 21/Dec/21  Updated: 27/Oct/22

Status: Accepted
Project: Magnolia
Component/s: testing
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Michael Duerig Assignee: Michael Duerig
Resolution: Unresolved Votes: 0
Labels: artt, foundation_team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-8188 Lightweight repository setup for tests Closed
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)
Epic Link: Basic JUnit 5
Team: Foundation

 Description   

MAGNOLIA-8188 introduced JUnit 5 extensions along with corresponding annotations for setting up Magnolia unit tests that need a component provider and/or JCR repository.

In a further step we should make an effort to move unit testing related extensions, tooling and utilities to its own module. One idea is to move to an new module unit-test-support under the test-framework project. OTHO, since the extensions for setting up a component provider and a JCR repository depend on magnlia-core, this might not be the right project to move to.

Previous discussion: https://git.magnolia-cms.com/projects/PLATFORM/repos/main/pull-requests/1021/overview?commentId=90381


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