requirements_for_test.txt

-r requirements.txt
flake8==3.7.9
moto==1.3.14
pytest==5.3.2
pytest-env==0.6.2
pytest-mock==2.0.0
pytest-cov==2.8.1
pytest-xdist==1.31.0
freezegun==0.3.12
requests-mock==1.7.0
# used for creating manifest file locally
jinja2-cli[yaml]==0.7.0
Initial version of the notify-notifications-api 2015-11-18 17:02:25 +00:00			`-r requirements.txt`
bump requirements 2019-11-18 15:48:38 +00:00			`flake8==3.7.9`
			`moto==1.3.14`
bump test requirements 2020-01-06 16:07:06 +00:00			`pytest==5.3.2`
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`
bump test requirements 2020-01-06 16:07:06 +00:00			`pytest-mock==2.0.0`
bump requirements 2019-11-18 15:48:38 +00:00			`pytest-cov==2.8.1`
bump test requirements 2020-01-06 16:07:06 +00:00			`pytest-xdist==1.31.0`
bump requirements 2019-11-18 15:48:38 +00:00			`freezegun==0.3.12`
			`requests-mock==1.7.0`
add jinja2-cli to dev requirements 2019-04-11 15:05:44 +01:00			`# used for creating manifest file locally`
Bump utils to bring in changes to logging Freezing the requirements changes the Werkzeug version to 0.16.0, which requires a change in how we import an exception (https://github.com/pallets/werkzeug/blob/master/CHANGES.rst#version-0160) 2019-10-23 16:14:39 +01:00			`jinja2-cli[yaml]==0.7.0`