pytest.ini

[pytest]
testpaths = tests
env =
    NOTIFY_ENVIRONMENT=test
    REDIS_ENABLED=0
addopts = -p no:warnings
xfail_strict = true
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]`
			`testpaths = tests`
			`env =`
			`NOTIFY_ENVIRONMENT=test`
remove `REDIS_ENABLED` flag from creds you can still use this flag locally but we have it enabled for all environments and it doesn't need to be toggleable from credentials as it isn't a secret value. If we wish to turn redis off for a specific environment we can create a PR to change the config. 2022-04-22 12:05:19 +01:00			`REDIS_ENABLED=0`
Quieten output for pytest This avoids being verbose by default, which is consistent with how we configure pytest for the admin app [1]. [1]: https://github.com/alphagov/notifications-admin/blob/master/pytest.ini#L16 2021-03-08 17:44:48 +00:00			`addopts = -p no:warnings`
don't expire email sign in codes on use we're seeing issues with email clients sniffing links, and causing them to expire before the user gets a chance to click on them. Temporarily disable the expiry while we work on a more permanent solution. The link will still expire after half an hour, and sms codes aren't affected by this change 2020-05-04 11:48:03 +01:00			`xfail_strict = true`