-
Notifications
You must be signed in to change notification settings - Fork 23
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
Focused tests and describes #17
Comments
We already have 3 × 3 functions for creating suites/contexts/examples. Any further addition of focussing variants (9 more functions each!) would be a bad idea, imho. Instead we should consider adding support for tagging one's suites/contexts/examples, with which in place one could realize skipping by simply negatively filtering for a given tag. The same applies to Skipped tests and describes. |
I don't agree. It works very well on other test suites so I don't see any reason to diverge on that. Yes, tagging would do it. Or it could not, and just bring creep to our lib when we have a very specific and narrow need. Or tagging could be used in intern with an another method on the frontend. |
Do we want a public of 27+ (( We would need to store an |
The famous
fit
, andfdescribe
!Role: when used, only the focused tests are run. This needs a change in design to report to the runner that we are in focus mode. Not big, though.
Note: if #6 or #5 are implemented, the aliases also needs their focused counterpart.
The text was updated successfully, but these errors were encountered: