-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Provide a way to NOT inherit extensions in nested containers or methods #1842
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
Comments
Test authors should be in full-charge to decide what resource is to be used where. Extension authors should provide means to configure/setup that requirement using the existing model. If the extension model lacks such configuration, we need to improve it. Said that, I favor a generic and built-in |
I guess Moreover, it's yet another mechanism to annotate and modify test behaviour - making things even more complicated and offering one more option for the same or very similar problems. |
With extensions comes complexity... With |
@testcontainers and other long-living resources are a perfect use-case: https://twitter.com/philipp_hauer/status/1112757852685430785 I'm preparing a Java 8-based |
This is a duplicate of or subtask of #506. |
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. Thank you for your contribution. |
This issue has been automatically closed due to inactivity. If you have a good use case for this feature, please feel free to reopen the issue. |
Sometimes an extension should not be applied to nested containers, e.g. if the extension wants to open and close a resource just once per annotated container. It seems to me that currently any registered extension will also be applied to its children and I couldn't find a way to switch that off.
The workarounds I can think of require strange things like storing the first context object in order to compare the current context object with it. I might be missing something, though.
Related Issues
The text was updated successfully, but these errors were encountered: