WTES-29: JUnit 5 extension for AemContext

[karollewandowski]

This is some kind of draft for feature described here: https://wcm-io.atlassian.net/browse/WTES-29.
Few words about how it works:
If test lifecycle method (@BeforeEach, @Test, @AfterEach) has AemContext parameter, then it will be created if not exists, or taken from context store. Parameter can be of AemContext abstract type - default context which is ResourceResolverMockAemContext will be created in such case. All 3 lifecycle methods must have matching context parameter. In case we inject JcrOakAemContext in @BeforeEach and JcrMockAemContext in @Test, then exception will be thrown with hint for developer what is wrong (it could be improved to print it in more readable and easier to understand way).

[jenslauterbach]

Any updates on this? We would like to us JUnit 5 and aem-mock in our current project.

So we would very much like to see official JUnit 5 support.

[stefanseifert]

we will definitely support it - active development paused for some time because the other junit5-related tooling was quite flaky at beginning of the year (e.g. in mockito, maven/surefire) - but there was some progress on this side. i plan to take up work on it soon.
the main discussion/work ticket is https://wcm-io.atlassian.net/browse/WTES-29.