Open johnhawkinson opened 8 months ago
Thanks for filing. We'll get this cleaned up.
ok this issue explains a lot. +1 confusing for new contributors
I also agree and I think we need a way to pass in just the specific court you want to test inside of tests. I shouldn't have to run 200 state courts just to generate or test Wyoming.
There is so much wrong with the testing documentation, it's really annoying to figure out how to run tests if you're not super-steeped in this stuff.
tl;dr
Run all tests with
Or, for an specific module:
but actually
README.rst
tells us to usetox
as a test runner, but that fails:This seems to be a bad
tox.ini
file.The actual test runner we do use in the github tests claims to be deprecated, but we use it anyhow (
python setup.py test
)and it seems to do much the same thing aspython -m unittest -v
.The example in
README.rst
ispython3 -m unittest -v tests.local.test_DateTest.DateTest.test_various_date_extractions
but that gives:it looks like you need to prefix
tests.local
, as:python3 setup.py test -s tests.local.test_DocketParseTest.DocketAnonymizeTest.test_anonymize_bankruptcy
anyhow
Somebody who understands how this should work should fix the documentation to be accurate and usable and consistent with what the Github tests do (that is three work items).
I am trying to actually get timely stuff done, so this is off my plate.