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.8.1
pytest-mock==1.11.2
pytest-xdist==1.27.0 # pyup: <1.28.0
beautifulsoup4==4.8.1
freezegun==0.3.12
flake8==3.7.9
flake8-bugbear==19.8.0
flake8-print==3.1.4
requests-mock==1.7.0
# used for creating manifest file locally
jinja2-cli[yaml]==0.7.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`
bump reqs utils bump, and a bunch of test dependencies can't bump pytest-xdist as it requires pytest>4 2019-11-18 14:56:56 +00:00			`pytest-cov==2.8.1`
			`pytest-mock==1.11.2`
			`pytest-xdist==1.27.0 # pyup: <1.28.0`
			`beautifulsoup4==4.8.1`
Combine test-related Pyup changes 2019-07-03 13:47:57 +01:00			`freezegun==0.3.12`
bump reqs utils bump, and a bunch of test dependencies can't bump pytest-xdist as it requires pytest>4 2019-11-18 14:56:56 +00:00			`flake8==3.7.9`
Do extra code style checks with flake8-bugbear Flake8 Bugbear checks for some extra things that aren’t code style errors, but are likely to introduce bugs or unexpected behaviour. A good example is having mutable default function arguments, which get shared between every call to the function and therefore mutating a value in one place can unexpectedly cause it to change in another. This commit enables all the extra warnings provided by Flake8 Bugbear, except for the line length one (because we already lint for that separately). It disables: - _B003: Assigning to os.environ_ because I don’t really understand this - _B306: BaseException.message is removed in Python 3_ because I think our exceptions have a custom structure that means the `.message` attribute is still present 2019-11-01 10:43:01 +00:00			`flake8-bugbear==19.8.0`
bump reqs utils bump, and a bunch of test dependencies can't bump pytest-xdist as it requires pytest>4 2019-11-18 14:56:56 +00:00			`flake8-print==3.1.4`
			`requests-mock==1.7.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`
bump reqs utils bump, and a bunch of test dependencies can't bump pytest-xdist as it requires pytest>4 2019-11-18 14:56:56 +00:00			`jinja2-cli[yaml]==0.7.0`