Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
62 lines (39 sloc) 1.95 KB
description
I decided to write a very short introduction to pytest, so people would not hate me for sending them RTFD links.

PyTest 101

List the tests

pytest --collect-only

Run only specific tests

If you want to run only tests that have 'foo' in their name or path, it is as easy as:

pytest -k foo

Limit which tests run by using markes

Test markers are like ansible tags, just some labels which can be assigned to tasks and you can decide which one you want to run or skip. They can be hardcoded in test definition or added dynamically.

# list markers available:
pytest --markers

# run only tests with a foo mark but without bar mark.
pytest -m foo -m "not bar"

Control stdout and stderr capture

Sometimes you may want to see, in real time, the output of various executed commands. This means that you may want to disable the default capturing of stdout/stderr.

pytest -s

{% hint style="info" %} On my local machine I defined `PYTEST_OPTS=-s` so I don't need to remember adding it each time. Still, on CI usually we do not want to do this because disabling capture means that pytest would generate a report without stdout. {% endhint %}

As an more advanced hint for tox users, you can also add {tty:-s} inside your tox.ini file, which mainly means that capture will be disabled when run on an interactice console (your terminal) but not on CI. Keep in mind that this option is relatively new to tox. And yes, you could also use this feature to trigger the debugger via --pdb.

Running tests in parallel

Keep in mind that the reult of runing tests in parallel depends a lot on how they were written. It is not uncommon to go into problems when running tests in parllel.

Default behavior is to avoid running in parallel.

# auto select number of processes based on your vCPU count
tox -n auto
You can’t perform that action at this time.