requirements_for_test.txt

-r requirements.txt
isort==5.10.1
pytest==7.1.2
pytest-env==0.6.2
pytest-mock==3.7.0
pytest-xdist==2.5.0
beautifulsoup4==4.11.1
freezegun==1.2.1
flake8==4.0.1
flake8-bugbear==22.4.25
flake8-print==5.0.0
moto==3.1.7
requests-mock==1.9.3
# used for creating manifest file locally
jinja2-cli[yaml]==0.8.2
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`
Update test dependencies to latest versions 2022-05-05 13:40:24 +01:00			`pytest==7.1.2`
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 test dependencies to latest versions 2022-05-05 13:40:24 +01:00			`beautifulsoup4==4.11.1`
			`freezegun==1.2.1`
Update flake8 from 3.9.2 to 4.0.1 2021-10-11 14:56:10 +01:00			`flake8==4.0.1`
Update test dependencies to latest versions 2022-05-05 13:40:24 +01:00			`flake8-bugbear==22.4.25`
			`flake8-print==5.0.0`
			`moto==3.1.7`
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 This results in some new errors from flake8-bugbear: ``` B020: Loop control variable overrides iterable it iterates ``` I can't see an issue with the places that we do this, so have ignored these warnings. If we keep getting these and they look fine, we can create a global rule to ignore B020. 2022-04-06 11:35:14 +01:00			`jinja2-cli[yaml]==0.8.2`