-
Notifications
You must be signed in to change notification settings - Fork 34
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
JUnit 5: Support @Nested
classes
#26
Comments
This is a known issue. We have an internal bug open for this, but not prioritized yet because we don't use JUnit5 internally and it's hard to get a sense of the demand for this outside of Google. |
@TestParameterInjectorTest
in @Nested
class@Nested
classes
@nymanjens Oh, I'm glad this was reported internally, too! Thanks for letting me know. And no worries, I've inferred from Google's open source code over the years that you're still stuck on JUnit 4, so I completely understand that other things have taken and will take priority. :) Would you be open to a contribution? I know this isn't the usual policy for Guava et al, but I'm unsure about this project. In the meantime, I'll use JUnit 5's built-in |
Yes, although this @nested stuff might need some changes to the code that is shared between junit4 and junit5 internally (it is copied to two different locations before exporting it to github), and so it might be a bit harder to backport, but certainly not impossible. |
Okay, good to know, thanks for the warning. I'll see if I can take a stab at this in the near future, then. |
@nymanjens Actually it doesn't seem I'll be able to look into this any time soon, so feel free to assign this story to someone else. |
If one runs an
@TestParameterInjectorTest
test method inside an inner class annotated with JUnit 5's@Nested
annotation, it throws the following stack trace.Example
Stack trace
The text was updated successfully, but these errors were encountered: