requirements_for_test.txt

-r requirements.txt
pycodestyle==2.3.1
pytest==3.2.3
pytest-mock==1.6.3
pytest-cov==2.5.1
pytest-xdist==1.20.0
coveralls==1.2.0
freezegun==0.3.9
requests-mock==1.3.0
# optional requirements for jsonschema
strict-rfc3339==0.7
rfc3987==1.3.7
Initial version of the notify-notifications-api 2015-11-18 17:02:25 +00:00			`-r requirements.txt`
Use pycodestyle instead of PEP8 PEP8 was renamed to pycodestyle; this issue explains why: https://github.com/PyCQA/pycodestyle/issues/466 This commit changes our tests to use pycodestyle instead of pep8. It also means: - making a couple of whitespace changes to appease the linter - disabling warnings for bare `Except`s (ie `Except` instead of `Except ValueError`) – this seems like a sensible thing to catch but I’m not going to make meaningful code changes in this commit 2017-02-01 09:19:32 +00:00			`pycodestyle==2.3.1`
Update pytest from 3.2.2 to 3.2.3 2017-10-04 22:18:02 +01:00			`pytest==3.2.3`
Update pytest-mock from 1.6.2 to 1.6.3 2017-09-16 01:23:26 +01:00			`pytest-mock==1.6.3`
bump test requirements also ignore celery improvements 2017-07-25 11:40:12 +01:00			`pytest-cov==2.5.1`
run tests in multiple threads at once previously we didn't do this because the tests all used the same DB (test_notifications_api), however @minglis shared a snippet that simply creates one test db per thread. 2017-08-23 14:46:40 +01:00			`pytest-xdist==1.20.0`
Update coveralls from 1.1 to 1.2.0 2017-08-16 04:20:36 +01:00			`coveralls==1.2.0`
bump test requirements also ignore celery improvements 2017-07-25 11:40:12 +01:00			`freezegun==0.3.9`
			`requests-mock==1.3.0`
Small refactor to how notification_schemas are tested. My local build was not always getting the optional requirement for the jsonschema uri format checker (rfc3987). The requirement has been added to the requirements_for_test file. I changed the tests to validate the response schema from the post_notifications tests, this way we can tell if we are breaking the contract. This showed that the email_from was not returning the entire email address but just the username, that has been corrected here. Removed the response schema validation tests since they are not being testing in the post notification tests. 2017-09-11 11:10:45 +01:00			`# optional requirements for jsonschema`
add public contract tests use jsonschema to test the GET /notification/{} endpoint to highlight any key name/format/type changes 2016-08-30 15:54:22 +01:00			`strict-rfc3339==0.7`
Small refactor to how notification_schemas are tested. My local build was not always getting the optional requirement for the jsonschema uri format checker (rfc3987). The requirement has been added to the requirements_for_test file. I changed the tests to validate the response schema from the post_notifications tests, this way we can tell if we are breaking the contract. This showed that the email_from was not returning the entire email address but just the username, that has been corrected here. Removed the response schema validation tests since they are not being testing in the post notification tests. 2017-09-11 11:10:45 +01:00			`rfc3987==1.3.7`