Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use new extension context scope in core extensions #4065

Merged
merged 5 commits into from
Oct 11, 2024

Conversation

marcphilipp
Copy link
Member

Overview

  • Use new scope in TimeoutExtension
  • Use new scope in RepetitionExtension
  • Use new scope in ParameterizedTestParameterResolver
  • Use new scope in TestReporterParameterResolver
  • Use new scope in TestInfoParameterResolver

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


Definition of Done

@marcphilipp marcphilipp self-assigned this Oct 10, 2024
Base automatically changed from marc/replace-annotation-with-extension-method to main October 11, 2024 13:58
An error occurred while trying to automatically change base from marc/replace-annotation-with-extension-method to main October 11, 2024 13:58
@marcphilipp marcphilipp force-pushed the marc/core-extensions-scope-adoption branch from 108047c to 2fd2439 Compare October 11, 2024 14:05
@marcphilipp marcphilipp marked this pull request as ready for review October 11, 2024 14:05
This extension is not affected by the change in behavior since
annotating test class constructors with `@Timeout` is not supported.
This extension is not affected by the change in behavior since it did
not use the supplied `ExtensionContext`.
This extension is not affected by the change in behavior since it does
not support resolving parameters for test class constructors.
When injecting `TestReporter` into test class constructors the published
report entries are now associated with the test method rather than the
test class unless the test instance lifecycle is set to `PER_CLASS` (in
which case they will continue to be associated with the test class).
When injecting `TestInfo` into test class constructors it now contains
data of the test method the test class instance is being created for
unless the test instance lifecycle is set to `PER_CLASS` (in which
case it continues to contain the data of the test class).
@marcphilipp marcphilipp force-pushed the marc/core-extensions-scope-adoption branch from 2fd2439 to 1e1f92e Compare October 11, 2024 14:20
@marcphilipp marcphilipp merged commit b083686 into main Oct 11, 2024
15 checks passed
@marcphilipp marcphilipp deleted the marc/core-extensions-scope-adoption branch October 11, 2024 14:29
@marcphilipp marcphilipp added this to the 5.12 M1 milestone Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant