You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jest won't report that as a test so wondering if it should be reported as an error. if it should be reported should we put that in valid-describe or in a standalone rule called no-standalone-expect
thoughts?
The text was updated successfully, but these errors were encountered:
I like this idea. A separate rule throwing if an expect is outside of a test case might make sense? Potentially with a flag that just disallows it in hooks and describes (so people can use helper functions for shared assertions), maybe? I don't think it needs to be coupled to valid-describe. Could stick it in valid-expect, but I think that's already getting super advanced and a separate rule makes more sense. Maybe not, though 🙂
curious if we can/should modify valid-describe to report an error if it finds an expect in a describe.
for example:
jest won't report that as a test so wondering if it should be reported as an error. if it should be reported should we put that in valid-describe or in a standalone rule called
no-standalone-expect
thoughts?
The text was updated successfully, but these errors were encountered: