requirements_for_test.txt

-r requirements.txt
isort==4.3.21
pytest==3.10.1  # pyup: <4.0.0
pytest-env==0.6.2
pytest-cov==2.7.1
pytest-mock==1.10.4
pytest-xdist==1.27.0
coveralls==1.8.1
beautifulsoup4==4.7.1
freezegun==0.3.12
flake8==3.7.7
flake8-print==3.1.0
requests-mock==1.6.0
# used for creating manifest file locally
jinja2-cli[yaml]==0.6.0
Initial creation of notify-admin-frontend 2015-11-18 16:19:40 +00:00			`-r requirements.txt`
Combine test-related Pyup changes 2019-07-03 13:47:57 +01:00			`isort==4.3.21`
Stop Pyup trying to upgrade us to Pytest 4 There’s no point until we’ve changed our code to conform. 2019-03-25 12:04:42 +00:00			`pytest==3.10.1 # pyup: <4.0.0`
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`. 1. https://github.com/MobileDynasty/pytest-env 2. https://docs.pytest.org/en/latest/customize.html#confval-testpaths 2018-02-14 09:49:27 +00:00			`pytest-env==0.6.2`
Combine test-related Pyup changes 2019-07-03 13:47:57 +01:00			`pytest-cov==2.7.1`
			`pytest-mock==1.10.4`
Update pytest-xdist from 1.26.1 to 1.27.0 2019-03-20 23:27:09 +00:00			`pytest-xdist==1.27.0`
Combine test-related Pyup changes 2019-07-03 13:47:57 +01:00			`coveralls==1.8.1`
Update beautifulsoup4 from 4.7.0 to 4.7.1 2019-01-07 01:07:37 +00:00			`beautifulsoup4==4.7.1`
Combine test-related Pyup changes 2019-07-03 13:47:57 +01:00			`freezegun==0.3.12`
Update flake8 from 3.7.6 to 3.7.7 2019-02-25 16:53:28 +00:00			`flake8==3.7.7`
Update flake8-print from 3.0.1 to 3.1.0 2018-02-11 16:39:14 +00:00			`flake8-print==3.1.0`
Combine test-related Pyup changes 2019-07-03 13:47:57 +01:00			`requests-mock==1.6.0`
move manifest to single jinja template uses the same pattern as other apps. Infers route based on app name, you can declare more in the dict at the top if you need to. 2019-04-12 11:05:45 +01:00			`# used for creating manifest file locally`
			`jinja2-cli[yaml]==0.6.0`