Description
openedon Apr 2, 2018
Feature Request
I am looking for a straightforward stable API for testing Extensions that would offer deep insights when meta-testing the Extension (think something similar to what is provided via the SummaryGeneratingListener, but with finer grained information reported).
Context here is that testing extensions via meta-testing (having a test that tests other test runs), I found it to be super helpful for getting insights around the test executions that occur based on how my extension may or may not affect them.
ExecutionEventRecorder seems to have some functionality that would be helpful in getting a deep insight to what a custom Extension might be doing, but it looks like it's not published as an API to consumers?
And some digging around led me to find things like ExecutionReportListener exist in the wild (see relevant SO question: https://stackoverflow.com/questions/46841243/how-to-test-extension-implementations), but it still has some holes in it's implementation. For example, it doesn't propagate information like test run duration, start and end times, test hierarchy, etc.
I took a stab at rolling some custom things to test the new Junit5 extension docker-compose-rule in this branch (full PR here: palantir/docker-compose-rule#223) that include the metadata I was referring too above, but wanted to know if there was a better way of doing it, or if something was published already. If not, I would be requesting this functionality from Junit5.
