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
[new-rule] Enforce top level describe #401
Comments
Sure, I'm down with that 🙂 |
Hi! That's something I was looking for as well and I would like to give it a try by opening a PR. Does it work for you? 🙂 |
Go for it! |
That would be awesome @thomlom 🙏 |
🎉 This issue has been resolved in version 22.16.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Amazing, this is perfect. A big thanks to both of you 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello everyone,
Jest, and most testing library, let you write and organise your tests as you want, which is good but it can become a mess with large testing codebase.
(Somewhat similar to #362 and
no-standalone-expect
)It would be super cool to have a rule to enforce a top-level describe and make sure no
test
,it
,beforeAll
etc... can live outside this describe.Maybe it can be something like:
require-top-level-describe
or
no-standalone-expect
=>
no-standalone: ['error', ['test', 'hook', 'expect']]
What do you think?
The text was updated successfully, but these errors were encountered: