[MAGNOLIA-8268] Support parametrisations for @MagnoliaRepositoryTest and @MagnoliaTest Created: 21/Dec/21  Updated: 24/Jan/22  Resolved: 24/Jan/22

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

Type: Improvement Priority: Neutral
Reporter: Michael Duerig Assignee: Michael Duerig
Resolution: Fixed Votes: 0
Labels: artt
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:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Basic JUnit 5

 Description   

Currently both JUnit 5 extensions @MagnoliaTest and @MagnoliaRepositoryTest do not support customisations. Their previous counterparts (MgnlTestCase and RepositoryTestCase) provided various hooks for e.g. injecting custom repository configurations files, custom properties, module registry, repository manager, etc.

With this ticket we should identify which of these customisations we also need for the new extensions and how we can provide them. Possible approaches include:

  • adding attributes to the test annotations
  • using @RegisterExtension for more complicated cases where parameters are only available at runtime
  • for even more elaborate cases test writers could use and evolve RepositoryConfiguration directly and might even derive further specific extensions when necessary / useful

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