Write dependent integration tests. See my pycon talk.
Project description
Entest
See tests/example.py
.
To have a test implicitly depend on all other tests use run_last
flag. This is the case for teardown of critical resources for example users.
To have all tests implicitly depend on a given test place it closer to the root of the graph.
Use setup_setup
to take advantage of depends_on
default behavior. (i.e. for the first decorated function in a module TEST_ROOT
is taken do be the previous test)
To have a test depend on another test NOT being run use without
flag. This is usefull for testing error flows.
** Right now this does not work correctly **
Contributing
Please do not maintain a fork! Make a pull request and if it is not obviously bad I will merge it in a timely manner.
I would like to change a lot of things structure-wise, but API will stay the same. In particular:
depends_on
decorator with kwargsprevious
,run_last
andwithout
.STATUS
classificator. I see how it can be misused easily, but I will still ship this footgun.
Run tests
entest tests/onboarding_api/test_happy_path.py --graph
entest tests/onboarding_api/test_happy_path.py
entest tests/onboarding_api/test_happy_path.py --env env_name tests/spam_users.py
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.