Merge remote-tracking branch 'origin/main' into add-resource-container-selector-resolver

Author: mpkorstanje

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,10 +1,11 @@
 ---
-name: Bug report
+name: Report a bug or regression
 about: Create a report to help us improve
-
+type: Bug
+labels: ["type: bug"]
 ---
 
-<!-- Please provide us the version of JUnit 5 you are using and, if possible, a failing unit test with your bug report. Don't forget to describe the rationale for this issue (e.g. expected vs. actual behavior). -->
+<!-- Please provide us the version of JUnit 5 you are using and, if possible, a failing unit test with your bug report. Don't forget to describe the rationale for this issue (e.g. expected vs. actual behavior). Please also mention where it's a regression compared to a previous version. -->
 
 ## Steps to reproduce
 

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Ask a question
+    url: https://github.com/junit-team/junit5/discussions/categories/q-a
+    about: Please ask and answer questions here
+  - name: Ask a question (Stack Overflow)
+    url: https://stackoverflow.com/questions/tagged/junit5
+    about: Alternatively, ask questions here

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,7 +1,8 @@
 ---
-name: Feature request
+name: Request a feature or enhancement
 about: Suggest an idea for this project
-
+type: Feature
+labels: ["type: new feature"]
 ---
 
 <!-- Start by telling us what problem you’re trying to solve. Often a solution already exists! Please, don’t send pull requests to implement new features without first getting our support. -->

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,12 @@
+---
+name: Create a task
+about: Create a task for a specific piece of work
+type: Task
+labels: ["type: task"]
+---
+
+<!-- Please describe what needs to be done to consider this task completed. -->
+
+## Deliverables
+
+- [ ] ...

.github/ISSUE_TEMPLATE/task.md

@@ -32,7 +32,7 @@ jobs:
     - name: Check out repository
       uses: actions/checkout@eef61447b9ff4aafe5dcd4e0bbf5d482be7e7871 # v4
     - name: Initialize CodeQL
-      uses: github/codeql-action/init@c36620d31ac7c881962c3d9dd939c40ec9434f2b # v3
+      uses: github/codeql-action/init@f779452ac5af1c261dce0346a8f964149f49322b # v3
       with:
         languages: ${{ matrix.language }}
         tools: linked
@@ -44,4 +44,4 @@ jobs:
           -Dscan.tag.CodeQL \
           allMainClasses
     - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@c36620d31ac7c881962c3d9dd939c40ec9434f2b # v3
+      uses: github/codeql-action/analyze@f779452ac5af1c261dce0346a8f964149f49322b # v3

.github/workflows/codeql-analysis.yml

@@ -21,7 +21,7 @@ jobs:
       with:
         fetch-depth: 1
     - name: Install GraalVM
-      uses: graalvm/setup-graalvm@22cc13fe88ef133134b3798e128fb208df55e1f5 # v1
+      uses: graalvm/setup-graalvm@6f327093bb6a42fe5eac053d21b168c46aa46f22 # v1
       with:
         distribution: graalvm-community
         version: 'latest'

.github/workflows/main.yml

@@ -139,7 +139,6 @@ endif::[]
 :BeforeAllCallback:                          {javadoc-root}/org.junit.jupiter.api/org/junit/jupiter/api/extension/BeforeAllCallback.html[BeforeAllCallback]
 :BeforeEachCallback:                         {javadoc-root}/org.junit.jupiter.api/org/junit/jupiter/api/extension/BeforeEachCallback.html[BeforeEachCallback]
 :BeforeTestExecutionCallback:                {javadoc-root}/org.junit.jupiter.api/org/junit/jupiter/api/extension/BeforeTestExecutionCallback.html[BeforeTestExecutionCallback]
-:EnableTestScopedConstructorContext:         {javadoc-root}/org.junit.jupiter.api/org/junit/jupiter/api/extension/EnableTestScopedConstructorContext.html[@EnableTestScopedConstructorContext]
 :ExecutableInvoker:                          {javadoc-root}/org.junit.jupiter.api/org/junit/jupiter/api/extension/ExecutableInvoker.html[ExecutableInvoker]
 :ExecutionCondition:                         {javadoc-root}/org.junit.jupiter.api/org/junit/jupiter/api/extension/ExecutionCondition.html[ExecutionCondition]
 :ExtendWith:                                 {javadoc-root}/org.junit.jupiter.api/org/junit/jupiter/api/extension/ExtendWith.html[@ExtendWith]

documentation/src/docs/asciidoc/link-attributes.adoc

@@ -16,7 +16,8 @@ on GitHub.
 [[release-notes-5.11.3-junit-platform-bug-fixes]]
 ==== Bug Fixes
 
-* ❓
+* Fixed a regression in method search algorithms introduced in 5.11.0 when classes reside
+  in the default package and using a Java 8 runtime.
 
 [[release-notes-5.11.3-junit-platform-deprecations-and-breaking-changes]]
 ==== Deprecations and Breaking Changes

documentation/src/docs/asciidoc/release-notes/release-notes-5.11.3.adoc

@@ -47,24 +47,44 @@ support the discovery of class path resource based tests, analogous to the
 [[release-notes-5.12.0-M1-junit-jupiter-deprecations-and-breaking-changes]]
 ==== Deprecations and Breaking Changes
 
-* ❓
+* 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). If you require the `TestInfo` of the test class, you can implement a class-level
+  lifecycle method (e.g., `@BeforeAll`) and inject `TestInfo` into that method.
+* 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). If you want to publish report entries for the test
+  class, you can implement a class-level lifecycle method (e.g., `@BeforeAll`) and inject
+  `TestReporter` into that method.
 
 [[release-notes-5.12.0-M1-junit-jupiter-new-features-and-improvements]]
 ==== New Features and Improvements
 
+* New `--exclude-methodname` and `--include-methodname` options added to the
+  `ConsoleLauncher` to include or exclude methods based on fully qualified method names
+  without parameters. For example, `--exclude-methodname=^org\.example\..+#methodname`
+  will exclude all methods called `methodName` under package `org.example`.
 * In a `@ParameterizedTest` method, a `null` value can now be supplied for Java Date/Time
   types such as `LocalDate` if the new `nullable` attribute in
   `@JavaTimeConversionPattern` is set to `true`.
 * `ArgumentsProvider` (declared via `@ArgumentsSource`), `ArgumentConverter` (declared via
   `@ConvertWith`), and `ArgumentsAggregator` (declared via `@AggregateWith`)
   implementations can now use constructor injection from registered `ParameterResolver`
   extensions.
+* Extensions based on `TestTemplateInvocationContextProvider` can now allow returning zero
+  invocation contexts by overriding the new `mayReturnZeroTestTemplateInvocationContexts`
+  method.
+* The new `@ParameterizedTest(requireArguments = false)` attribute allows to specify that
+  the absence of arguments is expected in some cases and should not cause a test failure.
 * Allow determining "shared resources" at runtime via the new `@ResourceLock#providers`
   attribute that accepts implementations of `ResourceLocksProvider`.
-* `@EnableTestScopedConstructorContext` has been added to enable the use of a test-scoped
-  `ExtensionContext` while instantiating the test instance.
-  The behavior enabled by the annotation is expected to eventually become the default in
-  future versions of JUnit Jupiter.
+* Extensions that implement `TestInstancePreConstructCallback`, `TestInstanceFactory`,
+  `TestInstancePostProcessor`, `ParameterResolver`, or `InvocationInterceptor` may
+  override the `getTestInstantiationExtensionContextScope()` method to enable receiving
+  a test-scoped `ExtensionContext` in `Extension` methods called during test class
+  instantiation. This behavior will become the default in future versions of JUnit.
 * `@TempDir` is now supported on test class constructors.