Context of the Test is passed to the constructor when test instance is created

[svenkost]

Overview

This change will give a MethodExtensionContext instead of a ClassExtensionContext to the construction of a constructor for a Test(Template). Before this change, if a test was created, there was no context for what the test was run, now there is context and also the display-name can be taken from the context.

---

I hereby agree to the terms of the JUnit Contributor License Agreement.

---

Definition of Done

• There are no TODOs left in the code
• Method preconditions are checked and documented in the method's Javadoc
• Coding conventions (e.g. for logging) have been followed
• Change is covered by automated tests including corner cases, errors, and exception handling
• Public API has Javadoc and @API annotations
• Change is documented in the User Guide and Release Notes
• All continuous integration builds pass

[marcphilipp]

❌ I think we cannot simply change with which context we invoke these extension points. It's currently the container extension context for consistency with different test instance lifecycles. We could add an additional, optional context, though. 🤔

[svenkost]

That is also an idea, but it means that one method override gets multiple contexts instead of only one.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be closed if no further activity occurs. If you intend to work on this pull request, please reopen the PR. Thank you for your contributions.

[stale]

This pull request has been automatically closed due to inactivity. If you are still interested in contributing this, please ensure that it is rebased against the latest branch (usually main), all review comments have been addressed and the build is passing.