[MGNLTEST-454] Provide JUnit5 "replacement" for AbstractMagnoliaHtmlUnitTest Created: 01/Nov/23  Updated: 15/Nov/23

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

Type: Task Priority: Neutral
Reporter: Christoph Meier Assignee: Christoph Meier
Resolution: Unresolved Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 1.5d Time Spent: 1d 1h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLTEST-467 Make MagnoliaHttpClient more conveni... Sub-task Closed Christoph Meier  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: core-TF-features-bugs-improvements
Team: Foundation
Work Started:

 Description   

Context

We still have a good amount of JUnit4-tests in ce, dx-core  which extend AbstractMagnoliaHtmlUnitTest.
Rececently a new test-class extending AbstractMagnoliaHtmlUnitTest has been added.

BUT we want to get rid of JUnit4-tests.
AbstractMagnoliaHtmlUnitTest, AbstractMagnoliaIntegrationTest will be - or already are deprecated.

This said - core-TF should offer a "utility", e.g. a Junit5-extension providing similar functionality like the AbstractMagnoliaHtmlUnitTest.

Please note that AbstractMagnoliaHtmlUnitTest exposes objects from com.gargoylesoftware.htmlunit. From architecture point if view, we should rather avoid this.

Ideas

Maybe the existing JUnit5-extension HttpClientSupport with its MagnoliaHttpClient can be extended to reach provide the function(s)

 

TBD

List of required functions ...

 


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