You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apply suite configuration to tests selected by unique ID (#3694)
Tests in a suite selected by unique id did not receive their
configuration because this was only applied to the discovery request
builder when a suite class was selected. By splitting the processing of
configuration annotations and select and filter annotations, the
configuration can now always be applied prior to discovery.
Fixes#3693.
(cherry picked from commit 74bd85c)
Copy file name to clipboardExpand all lines: junit-platform-suite-commons/src/main/java/org/junit/platform/suite/commons/SuiteLauncherDiscoveryRequestBuilder.java
+65-6Lines changed: 65 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -254,23 +254,82 @@ public SuiteLauncherDiscoveryRequestBuilder enableImplicitConfigurationParameter
254
254
}
255
255
256
256
/**
257
-
* Configure the suite class for the suite launcher discovery request.
257
+
* Apply a suites annotation based configuration, selectors and filters to this builder.
258
258
*
259
-
* <p>This method processes annotations on the suite class to customize
260
-
* the suite discovery and execution.
261
-
*
262
-
* @param suiteClass the suite class to configure
259
+
* @param suiteClass the class to apply the annotations from;
260
+
* never {@code null}
263
261
* @return this builder for method chaining
262
+
* @since 1.11
263
+
* @see org.junit.platform.suite.api.Suite
264
+
* @deprecated use {@link #applyConfigurationParametersFromSuite} and/or {@link #applySelectorsAndFiltersFromSuite} instead.
0 commit comments