-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Comments
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: @kytrinyx How do I get this change pushed to live? |
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. |
I'm deploying exercism/docs@56020d8 now. |
@kytrinyx Thanks. I consider this issue closed then. If not, please reopen. |
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.
The text was updated successfully, but these errors were encountered: