requirements_for_test.txt

-r requirements.txt
pycodestyle==2.3.1
pytest==3.1.3
pytest-mock==1.6.0
pytest-cov==2.3.1
pytest-xdist==1.14
coveralls==1.1
moto==0.4.25
httpretty==0.8.14
beautifulsoup4==4.5.1
freezegun==0.3.7
Initial creation of notify-admin-frontend 2015-11-18 16:19:40 +00:00			`-r requirements.txt`
Use pycodestyle instead of PEP8 PEP8 was renamed to pycodestyle; this issue explains why: PyCQA/pycodestyle#466 This commit changes our tests to use pycodestyle instead of pep8. No changes to our code were required as a result. 2017-02-02 10:50:26 +00:00			`pycodestyle==2.3.1`
Update pytest from 3.0.2 to 3.1.3 2017-07-06 14:23:06 +01:00			`pytest==3.1.3`
Update pytest-mock from 1.2 to 1.6.0 2017-07-06 14:23:07 +01:00			`pytest-mock==1.6.0`
bump test requirements to most recent 2016-09-09 16:29:30 +01:00			`pytest-cov==2.3.1`
Run tests on multiple CPU cores We can make the tests run slightly faster by parallelizing them across multiple CPU cores: - from some casual testing locally, 2 cores gives the optimum speedup - Travis container-based builds have 2 CPU cores available[1] - the net gain is about 20%, or 2 seconds - unfortunately we can’t do this on the API because each test is still using the same instance of the database 1. https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments 2016-07-04 06:57:00 +01:00			`pytest-xdist==1.14`
Add code coverage - generates a code coverage report - triggers Coveralls on every Travis build - adds a badge to the README 2016-04-07 10:28:29 +01:00			`coveralls==1.1`
bump test requirements to most recent 2016-09-09 16:29:30 +01:00			`moto==0.4.25`
Upgrade requirements. With the upgrade of pep8 to 1.7.0 module imports are required to be at the top of the file, meaning I had to add a noqa line to some of the init files. Are those init files wrong or is pep8 too strict. 2016-04-21 09:30:33 +01:00			`httpretty==0.8.14`
bump test requirements to most recent 2016-09-09 16:29:30 +01:00			`beautifulsoup4==4.5.1`
			`freezegun==0.3.7`