-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Running the tests #309
Comments
Thinking about this (maybe I miss something) using Normally one would choose So one way would be to rewrite all the tests to the pythonic lighter |
The advantage pytest gave is it allowed you to run all tests for all exercises at one time. It helped people figure out what exercise they were on if they forgot, or if old solutions had regressions. It was implemented by the maintainer that came before me, and I just kept pytest because it was the one they had used. I also believe unittest has no way of doing failed test first, but that may not be important for the size of our exercises. |
The failfast option for So maybe we should rewrite TESTS.md to show the |
To make sure my last comment was understood, there is a difference between fail fast and failed first. Fail fast may be available in unittest, but it does not support running the failed test first the next time it is run. |
Okay, so Than I think we should rewrite the |
Isn't it better to run the tests like
python bob_test.py
? Without installing a third partypytest
The text was updated successfully, but these errors were encountered: