pytest.ini configuration - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of pytest with custom markers in pytest.ini

Given the following pytest.ini configuration and test code, what will be the output when running pytest with the marker filter -m slow?

PyTest

[pytest]
markers =
    slow: marks tests as slow

# test_sample.py
import pytest

@pytest.mark.slow
def test_slow():
    assert True

def test_fast():
    assert True

A Only <code>test_slow</code> runs and passes; <code>test_fast</code> is skipped.

B Both <code>test_slow</code> and <code>test_fast</code> run and pass.

C Only <code>test_fast</code> runs and passes; <code>test_slow</code> is skipped.

D No tests run because marker <code>slow</code> is not recognized.

💡 Hint

The -m option runs tests matching the given marker.

The pytest.ini declares the marker slow. Running pytest with -m slow runs only tests marked with @pytest.mark.slow. So test_slow runs and passes; test_fast is skipped.

❓ assertion

intermediate

Assertion behavior with pytest.ini addopts

If pytest.ini contains addopts = --maxfail=1 --tb=short, what will happen when two tests fail in a test suite?

A Pytest stops after the first failure but shows full tracebacks.

B Pytest runs all tests and shows full tracebacks for failures.

C Pytest runs all tests and shows short tracebacks.

D Pytest stops after the first failure and shows a short traceback.

💡 Hint

The --maxfail option limits failures before stopping.

The --maxfail=1 option stops pytest after the first failure. The --tb=short option shows shorter tracebacks. So pytest stops after one failure and shows a short traceback.

❓ locator

advanced

Correct pytest.ini section for configuring test paths

Which section header is correct in pytest.ini to specify the directory where pytest should look for tests using testpaths?

A

[pytest]
testpaths = tests

B

[pytest.ini]
testpaths = tests

C

[config]
testpaths = tests

D

[tool:pytest]
testpaths = tests

💡 Hint

The official pytest configuration section is [pytest].

The correct section header in pytest.ini is [pytest]. Other headers like [tool:pytest] are used in other config files but not pytest.ini.

🔧 Debug

advanced

Identify the error in pytest.ini configuration

Given this pytest.ini content, what error will pytest raise when running?

PyTest

[pytest]
markers =
    slow: marks tests as slow
    fast marks tests as fast

A pytest ignores the invalid marker and runs all tests normally.

B pytest raises a ConfigError due to missing colon in marker declaration.

C pytest raises a SyntaxError parsing pytest.ini.

D pytest runs but warns about unknown marker 'fast'.

💡 Hint

Check the marker syntax carefully.

The second marker line misses a colon after 'fast'. This causes pytest to raise a ConfigError about invalid marker syntax.

❓ framework

expert

Effect of pytest.ini on test discovery and execution

Consider this pytest.ini: [pytest] testpaths = tests python_files = check_*.py addopts = -v --disable-warnings What is the combined effect of these settings when running pytest without arguments?

A Pytest looks only in the 'tests' folder for all test files, runs tests quietly, and suppresses warnings.

B Pytest looks in all folders for files starting with 'check_' and ending with '.py', runs tests verbosely, and shows warnings.

C Pytest looks only in the 'tests' folder for files starting with 'check_' and ending with '.py', runs tests verbosely, and suppresses warnings.

D Pytest looks in all folders for all test files, runs tests quietly, and shows warnings.

💡 Hint

Check each pytest.ini option's effect on discovery and output.

The 'testpaths = tests' limits discovery to the 'tests' directory. 'python_files = check_*.py' limits test files to those matching that pattern. 'addopts = -v --disable-warnings' runs tests verbosely and disables warnings.