Skip to content
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

Skipped tests and describes #18

Open
mackwic opened this issue Jul 23, 2016 · 1 comment
Open

Skipped tests and describes #18

mackwic opened this issue Jul 23, 2016 · 1 comment

Comments

@mackwic
Copy link
Member

mackwic commented Jul 23, 2016

The famous xit and xdescribe !

When used, the runner print them as success, count them as skipped, and doesn't run them.

It needs a little change in design to tell the runner to skip them.

Note1: if #6 or #5 are implemented, the aliases also needs their focused counterpart.
Note2: could be nice to do it via the test name. It could also be a poor way to solve the problem without design change.

@regexident
Copy link
Collaborator

We already have 3 × 3 functions for creating suites/contexts/examples.

Any further addition of skipping 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 Focused tests and describes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants