-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Invoke lifecycle hooks around each dynamic test #735
Closed
ledoyen
wants to merge
1
commit into
junit-team:master
from
ledoyen:fix/lifecycle_hooks_around_dynamic_tests
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please explain in great detail the need to override the
execute()
method, not only here but also in the commit message.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I choose to override the
execute()
method here to prevent calls to before and after hooks around a container execution.This is because a hook implementation can not know on which (of a container or a test) it is executed.
I assumed that
@BeforeEach
meant before each test, in this particular case, unlike what's said in the annotations javadoc.A cleaner way can be to declare a new annotation
@BeforeEachTest
and let callback implementations know about the type of test (container or not).If this is something you prefer, I can give it a try.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless I'm mistaken, lifecycle callbacks currently apply to
@TestFactory
methods.So it appears that you have removed this functionality, which some people may depend on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At the moment, no, I don't think we want to introduce any additional lifecycle annotations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about invoking lifecycle callbacks around
@TestFactory
methods and around each dynamic tests and making implementations aware of the type (container or test) they are invoked on ?This could be done by adding an
isContainer:boolean
method to theTestExtensionContext
like on theTestDescriptor
interface.I tried to improve the
MockitoExtension
by adding a reset of mocked field / parameters in Store before each test.This is why I removed callback invocation around
@TestFactory
methods in favor of dynamic tests in the first place.