pytest.ini

[pytest]
testpaths = tests
env =
    NOTIFY_ENVIRONMENT=test
    MMG_API_KEY=mmg-secret-key
    LOADTESTING_API_KEY=loadtesting
    FIRETEXT_API_KEY=Firetext
    NOTIFICATION_QUEUE_PREFIX=testing
addopts = -n 4 -v -p no:warnings
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`
			`MMG_API_KEY=mmg-secret-key`
			`LOADTESTING_API_KEY=loadtesting`
			`FIRETEXT_API_KEY=Firetext`
			`NOTIFICATION_QUEUE_PREFIX=testing`
bump utils also remove the `read().splitlines()` pattern from csv.reader usage, as it's redundant. also add .vscode to gitignore to accomodate my hipster IDE choices, and add some lines to pytest.ini so just running `py.test` uses some useful flags 2019-08-02 12:41:03 +01:00			`addopts = -n 4 -v -p no:warnings`