More typical Junit5 extension scopes #8249
Merged
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
yschimke
changed the title
|
@swankjesse requesting post review. I think this might affect flakyness of some tests, as the scope of parameterised tests wasn't right. Landing and happy to revert it fix forward. |
swankjesse
reviewed
Apr 3, 2024
| get() { | ||
| return getOrComputeIfAbsent(storeKey) { | ||
| get() = | ||
| getStore(namespace).getOrComputeIfAbsent(this.uniqueId) { |
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.
A second attempt at #8171
Now following examples from TestInfo more strictly.
There are two classes of instances
a) constructor, before all, after all
b) test method, before each, before all