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
Describe the bug
Trying to follow the instructions in README.rst for running tests was .. not very helpful, and it ended up being easier to read python-package.yml. So here's some suggestions for fixing stuff that tripped me up
requirements-dev.txt does not exist, unless you first run pip install pip-tools; pip-compile requirements-dev.in. So a line with this should probably be added.
$ pytest -v tests
When giving examples I think it's good manner to use the long form of flags to be maximally helpful, so imo this should be pytest --verbose tests to be extra clear that it's not a required flag.
The text was updated successfully, but these errors were encountered:
Oh, pytest -v tests doesn't seem standard either. It should probably be make mototest and mention that docker is a thing. And that doesn't seem to require AWS credentials too??
make vtest or other bare pytest invocations gives me several failing tests, even with AWS credentials, but at least one of them is a straight-up incorrect testcase I'll open a separate issue for (#1041).
yea, the docs are all probably outdated. the regular tests don't require aws credentials because they use moto. The non moto tests are those not supported by moto that need to be run with someone's personal AWS creds
Describe the bug
Trying to follow the instructions in README.rst for running tests was .. not very helpful, and it ended up being easier to read python-package.yml. So here's some suggestions for fixing stuff that tripped me up
requirements-dev.txt
does not exist, unless you first runpip install pip-tools; pip-compile requirements-dev.in
. So a line with this should probably be added.pytest --verbose tests
to be extra clear that it's not a required flag.The text was updated successfully, but these errors were encountered: