You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a lot of heterogeneity in the quality of the tests. An audit-like process should attempt to identify/address (in no particular order):
What parts of the code have only smoke tests?
What parts of the tests are not getting run?
Commented-out
mangled names
miscellany likedef junk in discrete.tests.test_constrained
stranded in __main__ sections
incorrectly located in __main__ sections of non-test files.
Are there any xfailed tests that have been fixed? Or can be marked with strict=True?
A lot of effort went into creating the results files to compare against (props to our sm forebearers). Are these reproducible? (and if not, can they be made reproducible?)
In some cases results were subsequently "hand-edited" for various reasons. Are these well-documented?
Some "example" files have snuck into test directories; where should they go?
Can test runtime be significantly reduced by efficient use of pytest.fixtures?
Are there combinations of parameters that can be tested more thoroughly using pytest.mark.parametrize?
Can the tests be otherwise be made less verbose/clearer?
Other modernizations that should be made? e.g. IIUC assert_almost_equal is discouraged and assert_allclose should be used instead.
Are there places where assert_allclose tolerances can be reduced?
grep turns up 5 occurrences of "FIXME" and 218 occurrences of "TODO" in test directories
There are a whole bunch of occurrences of things like:
There is a lot of heterogeneity in the quality of the tests. An audit-like process should attempt to identify/address (in no particular order):
def junk
indiscrete.tests.test_constrained
__main__
sections__main__
sections of non-test files.strict=True
?sm
forebearers). Are these reproducible? (and if not, can they be made reproducible?)pytest.fixture
s?pytest.mark.parametrize
?assert_almost_equal
is discouraged andassert_allclose
should be used instead.assert_allclose
tolerances can be reduced?The TODO is reasonably clear and helpful, but the commented-out
True
and the commented-out fit parameters are not helpful in their current form.This is a pretty huge task. A few steps in this direction: #4941, #4936, #4932, #4907, #4875, #4863, #4506, #4488, #4305
The text was updated successfully, but these errors were encountered: