Load and register custom TestExecutionListener implementations automatically

[sormuras]

What about adding support for loading custom TestExecutionListener implementations via the Service API to the console launcher?

Enhance (and document) ExecuteTestsTask#registerListeners with:

ServiceLoader.load(TestExecutionListener.class)
  .forEach(launcher::registerTestExecutionListeners);

Or add the load and register functionality to the platform DefaultLauncher itself?

[marcphilipp]

I think we should add them to the DefaultLauncher not just when using ConsoleLauncher. I also proposed we do this in #542 (comment).

[marcphilipp]

@junit-team/junit-lambda Any objections?

[sbrannen]

No objections. Go for it!

[sbrannen]

Resolved in 3c52d95.

[marcphilipp]

This still needs to be documented in the User Guide and Release Notes. We haven't really used a consistent strategy to address that need in the past. We could reopen this issue, create a new one, or procrastinate until some poor guy wants to do a release and has to go through all the issues.

I'm in favor of the first option.

@junit-team/junit-lambda What do you think?

[sbrannen]

This still needs to be documented in the User Guide and Release Notes.

Oooooops. Yes... you are totally correct!

I'm in favor of reopening the original issue in such cases: no need to multiple issues for the same issue.

Since I prematurely closed it, I'll reopen it. 😉

[sbrannen]

In retrospect, we need to (re)define our Definition of Done for issues. Though perhaps we should discuss that amongst the team and then document it in the wiki (and of course actually adhere to the rules).

[sbrannen]

Actually, I'll create an issue to address the DoD.

[sbrannen]

See #593 regarding the Definition of Done.