forked from junit-team/junit5
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add resource container selector resolver #16
Draft
mpkorstanje
wants to merge
333
commits into
support-classpath-resources-scanning
Choose a base branch
from
add-resource-container-selector-resolver
base: support-classpath-resources-scanning
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Add resource container selector resolver #16
mpkorstanje
wants to merge
333
commits into
support-classpath-resources-scanning
from
add-resource-container-selector-resolver
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t file system temp directory (junit-team#3921) Closes junit-team#3910. --------- Co-authored-by: Marc Philipp <[email protected]>
…it-team#3924) Resolves junit-team#3923. --------- Co-authored-by: Christian Stein <[email protected]>
Add a flag to ParameterizedTest to control arguments requirement. This allows users to explicitly opt out from validation of arguments set count and silently skip a test if no arguments are provided In general, support TestTemplateInvocationContextProvider returning zero invocation contexts. Such providers must override new interface method to indicate that the framework should expect "no context returned" Resolves junit-team#1477
The new `--exclude-methodname` and `--include-methodname` options added of the `ConsoleLauncher` allow 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` in the `org.example` package or any of its subpackages. Resolves junit-team#3107.
`Class.getPackage()` returns `null` for the default package on Java 8. This is now handled by inspecting the fully qualified class name rather than throwing a `NullPointerException`. Fixes junit-team#4076.
…r-selector-resolver
…discovery/ClasspathResourceSelector.java Co-authored-by: Marc Philipp <[email protected]>
…12.0-M1.adoc Co-authored-by: Marc Philipp <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just viewing the diff between to PRs.