-
-
Notifications
You must be signed in to change notification settings - Fork 195
Consistent way to hide ignored test cases #955
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
Comments
Hi @Javran, and thanks for contributing! Sorry about the delay. Using |
Sorry, I was thinking about a design choice when I wrote that: the concern is if we override |
Would #1075 help in this case? |
@sshine it appears that #952 is completed? I noticed some unmerged PRs and thought they might be waiting for #952 given what you said, so just thought I would let you know |
Yes, it is. The premise for this issue can be re-assessed without blockers. |
I noticed that there isn't a consistent way regarding how some test cases are ignored, to name a few:
I'm wondering if you are open to the idea of using some hspec facilities like
configSkipPredicate
from Config so those ignored cases can be uncommented but still ignored without explicitly specifying it? (This is of course assumming that all test suites are using or can be adapted to use hspec)A potential strategy, for example, might be marking ignored tests by prefixing its description with
Ignored:
, and then instruct users to usestack test --ta="--skip=Ignored:"
and remove--skip
flag when they are up to the challenge.The text was updated successfully, but these errors were encountered: