requirements_for_test.txt

-r requirements.txt
isort==5.10.1
pytest==7.0.1
pytest-env==0.6.2
pytest-mock==3.7.0
pytest-xdist==2.5.0
beautifulsoup4==4.10.0
freezegun==1.1.0
flake8==4.0.1
flake8-bugbear==22.1.11
flake8-print==4.0.0
moto==3.0.5
requests-mock==1.9.3
# used for creating manifest file locally
jinja2-cli[yaml]==0.8.1
Stop locking non-test dependencies twice Currently we have a situation where we're not running tests against new versions of dependencies, as requirements_for_test.txt is not being kept in-sync with requirements.txt by pyup. Deploys are only working because Concourse silently ignores version issues. From a deployment log: awscli 1.18.211 has requirement PyYAML<5.4,>=3.10; python_version != "3.4", but you'll have pyyaml 5.4 which is incompatible. This switches to a single requirements file for test dependencies, in order to keep it in-sync with requirements.txt i.e. we run our tests against the same versions of dependencies that we deploy with, and the build fails if we try to use package versions that are not mutually compatible, as this example PR shows [1]. ERROR: Cannot install -r requirements_for_test.txt (line 17), -r requirements_for_test.txt (line 198) and pyyaml==5.4.1 because these package versions have conflicting dependencies. We shouldn't need to have fine-grained locking on test dependencies, beyond those we want to list manually in the file. [1]: https://github.com/alphagov/notifications-admin/pull/3804 2021-02-16 17:08:03 +00:00			`-r requirements.txt`
Bump all test dependencies 2022-03-02 14:36:27 +00:00			`isort==5.10.1`
			`pytest==7.0.1`
Update requirements - install patch for jinja2 vulnerability 2021-02-02 17:13:18 +00:00			`pytest-env==0.6.2`
Bump all test dependencies 2022-03-02 14:36:27 +00:00			`pytest-mock==3.7.0`
			`pytest-xdist==2.5.0`
Update beautifulsoup4 from 4.9.3 to 4.10.0 2021-10-11 14:56:09 +01:00			`beautifulsoup4==4.10.0`
Update freezegun from 0.3.12 to 1.1.0 2021-03-08 13:55:06 +00:00			`freezegun==1.1.0`
Update flake8 from 3.9.2 to 4.0.1 2021-10-11 14:56:10 +01:00			`flake8==4.0.1`
Bump all test dependencies 2022-03-02 14:36:27 +00:00			`flake8-bugbear==22.1.11`
Update flake8-print from 3.1.4 to 4.0.0 2021-03-08 13:55:08 +00:00			`flake8-print==4.0.0`
Bump all test dependencies 2022-03-02 14:36:27 +00:00			`moto==3.0.5`
Update requests-mock from 1.8.0 to 1.9.3 2021-05-31 14:54:12 +01:00			`requests-mock==1.9.3`
Stop locking non-test dependencies twice Currently we have a situation where we're not running tests against new versions of dependencies, as requirements_for_test.txt is not being kept in-sync with requirements.txt by pyup. Deploys are only working because Concourse silently ignores version issues. From a deployment log: awscli 1.18.211 has requirement PyYAML<5.4,>=3.10; python_version != "3.4", but you'll have pyyaml 5.4 which is incompatible. This switches to a single requirements file for test dependencies, in order to keep it in-sync with requirements.txt i.e. we run our tests against the same versions of dependencies that we deploy with, and the build fails if we try to use package versions that are not mutually compatible, as this example PR shows [1]. ERROR: Cannot install -r requirements_for_test.txt (line 17), -r requirements_for_test.txt (line 198) and pyyaml==5.4.1 because these package versions have conflicting dependencies. We shouldn't need to have fine-grained locking on test dependencies, beyond those we want to list manually in the file. [1]: https://github.com/alphagov/notifications-admin/pull/3804 2021-02-16 17:08:03 +00:00			`# used for creating manifest file locally`
Bump all test dependencies 2022-03-02 14:36:27 +00:00			`jinja2-cli[yaml]==0.8.1`