[MGNLTEST-111] Extract separate JcrFixture extension for bootstrapping/cleaning up content Created: 27/Oct/20  Updated: 26/Mar/21  Resolved: 04/Jan/21

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

Type: Improvement Priority: Neutral
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLTEST-135 CLONE - Extract separate extension fo... Closed
Relates
relates to MGNLTEST-138 Refactor existing new INT. tests rega... Closed
relates to MGNLTEST-146 CLONE - Refactor existing new INT. te... 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)
Date of First Response:
Epic Link: core-TF-features-bugs-improvements
Story Points: 3

 Description   
  • help leverage JUnit 5's composable extension model
  • shift the Selenium extension gradually towards single-responsibility

PR exists already => https://git.magnolia-cms.com/projects/PLATFORM/repos/test-framework/pull-requests/15/overview

Needs a rebase after MGNLTEST-102, likely will need another one after MGNLTEST-12.



 Comments   
Comment by Mikaël Geljić [ 11/Dec/20 ]

rdhar considering a timebox for TestEngine APIs / possibility of convenience for inferring jupiter extensions instead of having to list them all (see ArchUnit for an example implementation of such APIs)

Comment by Christoph Meier [ 05/Jan/21 ]

mgeljic - can you add a minimal "usage" instruction here about which annotation is recommended to use in which case. ... because I see that most of the self-tests now use the new annotation MagnoliaIntegrationTest, while test in ce still use the Selenium annotation.

I would then update the .md doc file in the test-framework ... beides rdhar did already planned to do the doc update in the context of his next tech.-talk.

Comment by Mikaël Geljić [ 05/Jan/21 ]

long story short, we should switch all @ExtendWith(Selenium.class) functional tests to @MagnoliaIntegrationTest eventually.

  • this could already be prepared on a PR, +/- the open discussion re: annotation naming
  • we have not moved CE/DX to test-framework 1.1.0 yet
  • eventually Selenium & JCR Fixtures should be lazy/non-obstrusive too, not a blocker for now
Generated at Mon Feb 12 07:45:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.