Skip to content

Ignore all tests except the first one by default #189

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

Closed
Ben-Baert opened this issue Jul 12, 2015 · 4 comments
Closed

Ignore all tests except the first one by default #189

Ben-Baert opened this issue Jul 12, 2015 · 4 comments

Comments

@Ben-Baert
Copy link

It'd be useful to have unittest.SkipTest decorators that ignores all but the first test. This way, you can try to make the first test work, once it works, delete the next unittest.SkipTest decorator, make the code pass that test, etc., instead of being overloaded by a barrage of tests that fail.

I've noticed that this approach seems to be used in some language tracks (e.g. Rust), but it'd be useful if this was standard in all tracks. I now do this manually, but it'd be nice if this was implemented as standard. Another approach is to group tests that test similar functionality together (ie. different testcase classes), and then ignore all but the first class. That way, you don't get error messages concerning functionality that you're not yet trying to deal with.

@Dog
Copy link
Contributor

Dog commented Jul 12, 2015

We have documentation for that workflow, but it doesn't seem to have been pushed to the live site.

You can find the documentation here:
https://github.com/exercism/xpython/blob/master/docs/WORKFLOW.md

@kytrinyx How do I get this change pushed to live?

@kytrinyx
Copy link
Member

At the moment the documentation is half-way between two systems. It needs to be in the docs site to go live. I'll copy it over.

@kytrinyx
Copy link
Member

I'm deploying exercism/docs@56020d8 now.

@Dog
Copy link
Contributor

Dog commented Jul 17, 2015

@kytrinyx Thanks. I consider this issue closed then. If not, please reopen.

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

No branches or pull requests

3 participants