[MAGNOLIA-8358] JUnit5 extensions for importing repository content Created: 22/Mar/22 Updated: 03/Jan/23 Resolved: 03/Jan/23 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | testing |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Michael Duerig | Assignee: | Michael Duerig |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | foundation_team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: | |
| Epic Link: | Basic JUnit 5 |
| Team: |
| Description |
| Comments |
| Comment by Christoph Meier [ 26/Dec/22 ] |
|
mduerig - is this still relevant? What other repo-content should be imported with a JUnit5 extension? |
| Comment by Michael Duerig [ 02/Jan/23 ] |
|
cmeier currently we still use the DataTransporter class for manually importing content in quite a few places. E.g. here. If the @Fixture and @Cleanup extensions cover (most) of these cases we can resolve this ticket as outdated. Otherwise it might make sense to adjust the requirements so we don't end up with multiple annotations for (nearly) the same thing. |
| Comment by Christoph Meier [ 03/Jan/23 ] |
|
mduerig , I think we can close it as outdated. As you said - Fixture and Cleanup do the job for Junit5-tests. Close it |
| Comment by Michael Duerig [ 03/Jan/23 ] |
|
Closing as per cmeier comment: https://jira.magnolia-cms.com/browse/MAGNOLIA-8358?focusedId=336600&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-336600 |