XFAIL, Command Line API | Rustam Zokirov

pytest - finds all test_ and _test files in all dirs
pytest my_dir - runs all test files inside particular directory
pytest test_4.py - runs test file
pytest test_4.py::test_add - runs test_add function

# TOP commands to use
pytest --collect-only # don't execute test
pytest -x  # –exitfirst
pytest -v --tb=no  # When a test fails, pytest lists the failures and what’s called a traceback, which shows you the exact line where the failure occurred.

# EXPRESSION -k
pytest -k "asdict or defaults" --collect-only # Let’s say you want to run the test_asdict() and test_defaults() tests.
pytest -v -k "asdict or defaults"

# MARKEXPR -m
"""
import pytest
... 
@pytest.mark.run_these_please 
def test_member_access():
...
"""
pytest -v -m 'run_these_please' test_api_exceptions.py
pytest -v -m 'smoke and get' test_api_exceptions.py  # test that had both smoke and get markers

pytest --maxfail=2 --tb=no
pytest --maxfail=1 --tb=no  # The same as pytest -x

-s and –capture=no  # Show print stdout

pytest --lf

pytest --ff

pytest -l tasks  # -l, –showlocals, local variables and their values are displayed with tracebacks for failing tests

pytest --durations=3 tasks  # Shows the 3 slowest tests 

pytest -rs test_unique_id_3.py # to see the reason why tests are skipped

## Fixtures
pytest --setup-show test_add.py -k valid_id # ← to see what setup and teardown methods were being used

pytest --fixtures # to list fixtures

pytest -v tasks/test_four.py::test_asdict # Running only one test

Every test essentially has three phases: call, setup, and teardown. Setup and teardown are also called *fixtures* and are a chance for you to add code to get data or the software system under test into a precondition state before the test runs, as well as clean up afterwards if necessary.

-v

Writes which test passed, failed

-tb=no