-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
parametrize more tests, move to test_liboffstes #18346
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
Conversation
no the point is usuability, you can run very specific tests, and see exactly what fails, while exercising lots of cases. these are silghtly more abstruse than a loop, but the above point wins. |
in some cases you might want to use |
I didn't think so, but it was worth asking. At one point with dateutil I tried testing every combination of several parameters and RAM usage spiked during pytest test collection, had to kill the process. This was a loop that would have been harmless (albeit poorly advised for other reasons) using older nose-yield-style tests. Let me a little gunshy. |
Codecov Report
@@ Coverage Diff @@
## master #18346 +/- ##
==========================================
- Coverage 91.38% 91.36% -0.02%
==========================================
Files 164 164
Lines 49790 49790
==========================================
- Hits 45501 45492 -9
- Misses 4289 4298 +9
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #18346 +/- ##
==========================================
- Coverage 91.38% 91.36% -0.02%
==========================================
Files 164 164
Lines 49790 49790
==========================================
- Hits 45501 45492 -9
- Misses 4289 4298 +9
Continue to review full report at Codecov.
|
thanks! |
Some tests currently in test_offsets belong in test_liboffsets, this moves them.
There is a test_shift_month in test_offsets and another in test_liboffsets. This combines them.
Continuing the process of making the big lists of tests in test_offsets use pytest.mark.parametrize. Is there any downside to doing this? e.g. when it collects the tests, will it hold them all in memory (instead of as a generator)?
git diff upstream/master -u -- "*.py" | flake8 --diff