requirements_for_test.txt

-r requirements.txt
flake8==3.7.6
moto==1.3.7
pytest==3.10.1  # pyup: <4
pytest-env==0.6.2
pytest-mock==1.10.1
pytest-cov==2.6.1
pytest-xdist==1.26.1
coveralls==1.6.0
freezegun==0.3.11
requests-mock==1.5.2
# optional requirements for jsonschema
strict-rfc3339==0.7
rfc3987==1.3.8
Initial version of the notify-notifications-api 2015-11-18 17:02:25 +00:00			`-r requirements.txt`
bump requirements pyup ignore pytest until we sort all the fixtures as functions issues 2019-02-19 16:17:33 +00:00			`flake8==3.7.6`
bump requirements, fix pyflake8 things, unpin botocore/awscli 2018-11-07 13:39:08 +00:00			`moto==1.3.7`
bump requirements pyup ignore pytest until we sort all the fixtures as functions issues 2019-02-19 16:17:33 +00:00			`pytest==3.10.1 # pyup: <4`
Automatically set environment vars before tests Sometimes you just wanna run some tests directly using the `pytest` command. But you’re in a new shell, and have forgotten to do `source environment_test.sh`. The screen fills with red, and your day just got a little bit worse. This commit will stop this from ever happening again, by making the setting environment variables part of running Pytest. It does this with a plugin called pytest-env[1]. pytest.ini is the standard way of configuring pytest. Creating this file where it didn’t exist before changes the behaviour of pytest, in that it will now look for tests in the same directory as the file, rather than defaulting to the `tests/` directory. So we also have to explicitly configure pytest[2] to tell it that it should only look in this directory. Otherwise it gets lost in the weeds of `node_modules`. This also changes the way that `SQLALCHEMY_DATABASE_URI` is overriden to the convention used by this plugin. 1. https://github.com/MobileDynasty/pytest-env 2. https://docs.pytest.org/en/latest/customize.html#confval-testpaths fixup! Remove environment_test.sh 2018-02-14 11:19:11 +00:00			`pytest-env==0.6.2`
reqs bump 2019-02-06 16:49:56 +00:00			`pytest-mock==1.10.1`
Update pytest-cov from 2.6.0 to 2.6.1 2019-01-07 02:12:39 +00:00			`pytest-cov==2.6.1`
reqs bump 2019-02-06 16:49:56 +00:00			`pytest-xdist==1.26.1`
bump requirements pyup ignore pytest until we sort all the fixtures as functions issues 2019-02-19 16:17:33 +00:00			`coveralls==1.6.0`
bump requirements also pyup ignore awscli and botocore because that complex mesh of dependency hell doesn't play will with pyup opening a new PR every time that botocore/awscli update (every few days) 2018-10-22 14:43:08 +01:00			`freezegun==0.3.11`
bump requirements 2018-08-03 11:35:10 +01:00			`requests-mock==1.5.2`
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`
bump requirements 2018-08-03 11:35:10 +01:00			`rfc3987==1.3.8`