[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: |
|
||||||||||
| Template: |
|
||||||||||
| Acceptance criteria: |
Empty
|
||||||||||
| Task DoR: |
Empty
|
||||||||||
| Epic Link: | core-TF-features-bugs-improvements | ||||||||||
| Team: | |||||||||||
| Work Started: |
| Description |
ContextWe still have a good amount of JUnit4-tests in ce, dx-core which extend AbstractMagnoliaHtmlUnitTest. BUT we want to get rid of JUnit4-tests. 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. IdeasMaybe the existing JUnit5-extension HttpClientSupport with its MagnoliaHttpClient can be extended to reach provide the function(s)
|