requirements_for_test.txt

-r requirements.txt
flake8==4.0.1
flake8-bugbear==22.1.11
isort==5.10.1
moto==3.0.5
pytest==7.0.1
pytest-env==0.6.2
pytest-mock==3.7.0
pytest-cov==3.0.0
pytest-xdist==2.5.0
freezegun==1.1.0
requests-mock==1.9.3
# used for creating manifest file locally
jinja2-cli[yaml]==0.8.1
Initial version of the notify-notifications-api 2015-11-18 17:02:25 +00:00			`-r requirements.txt`
Update flake8 from 3.8.4 to 4.0.1 And adds `noqa` to some non-errors which are being flagged. 2022-03-02 15:52:18 +00:00			`flake8==4.0.1`
Update flake8-bugbear from 20.11.1 to 22.1.11 And ignore a warning, since I did not think that in this case "Using .strip() with multi-character strings is misleading the reader". 2022-03-02 16:51:09 +00:00			`flake8-bugbear==22.1.11`
Bump all test dependencies which require no code changes 2022-03-02 17:18:32 +00:00			`isort==5.10.1`
			`moto==3.0.5`
			`pytest==7.0.1`
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`. This also changes the way that `SQLALCHEMY_DATABASE_URI` is overriden to the convention used by this plugin. 1. https://github.com/MobileDynasty/pytest-env 2. https://docs.pytest.org/en/latest/customize.html#confval-testpaths fixup! Remove environment_test.sh 2018-02-14 11:19:11 +00:00			`pytest-env==0.6.2`
Bump all test dependencies which require no code changes 2022-03-02 17:18:32 +00:00			`pytest-mock==3.7.0`
			`pytest-cov==3.0.0`
			`pytest-xdist==2.5.0`
Add tests for celery task superclass This requires upgrading freezegun, as time.monotonic wasn't frozen by v1.0. Note that we need to explicitly specify the base class for the task in the test, the reason for which is quite subtle: - Normally, by using the 'notify_api' fixture, the base class is set to NotifyTask automatically by running app.create_app [1]. - However, when run alongside other tests, the imports of files with other celery tasks cause the base class to be instantiated and cached as the default Celery one. This means none of our tests actually use our custom superclass when testing tasks. Because we can't run 'apply_async' directly (since this would require an actual Celery broker), we need to manually push/pop the request Context that's normally done as part of sending a task. Note also that we use a UUID as the name for a task, since these are global. We want to avoid the task polluting other tests in future, as well as make it clear the task is being reused. [1]: https://github.com/alphagov/notifications-api/blob/dea5828d0e708bc69916a98e2bff989a56112204/app/__init__.py#L113 2021-04-08 10:01:51 +01:00			`freezegun==1.1.0`
Bump all test dependencies which require no code changes 2022-03-02 17:18:32 +00:00			`requests-mock==1.9.3`
add jinja2-cli to dev requirements 2019-04-11 15:05:44 +01:00			`# used for creating manifest file locally`
Bump all test dependencies which require no code changes 2022-03-02 17:18:32 +00:00			`jinja2-cli[yaml]==0.8.1`