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

Commits on Oct 11, 2024

  1. Use new scope in TimeoutExtension

    This extension is not affected by the change in behavior since
    annotating test class constructors with `@Timeout` is not supported.
    marcphilipp committed Oct 11, 2024
    Configuration menu
    Copy the full SHA
    f9ebfd5 View commit details
    Browse the repository at this point in the history
  2. Use new scope in RepetitionExtension

    This extension is not affected by the change in behavior since it did
    not use the supplied `ExtensionContext`.
    marcphilipp committed Oct 11, 2024
    Configuration menu
    Copy the full SHA
    308a1b0 View commit details
    Browse the repository at this point in the history
  3. Use new scope in ParameterizedTestParameterResolver

    This extension is not affected by the change in behavior since it does
    not support resolving parameters for test class constructors.
    marcphilipp committed Oct 11, 2024
    Configuration menu
    Copy the full SHA
    4f606a8 View commit details
    Browse the repository at this point in the history
  4. Use new scope in TestReporterParameterResolver

    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).
    marcphilipp committed Oct 11, 2024
    Configuration menu
    Copy the full SHA
    1d0bee2 View commit details
    Browse the repository at this point in the history
  5. Use new scope in TestInfoParameterResolver

    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 committed Oct 11, 2024
    Configuration menu
    Copy the full SHA
    1e1f92e View commit details
    Browse the repository at this point in the history