setup.cfg configuration in PyTest - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of pytest with setup.cfg markers

Given the following setup.cfg configuration and test file, what will be the output when running pytest without any additional options?

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 Both tests are skipped.

B Only test_fast runs and passes; test_slow is skipped.

C Both tests run and pass.

D pytest raises an error due to unknown marker.

💡 Hint

Markers declared in setup.cfg do not skip tests by default.

Declaring markers in setup.cfg only registers them to avoid warnings. Tests marked with 'slow' still run unless explicitly filtered or skipped.

❓ assertion

intermediate

Correct assertion for test selection by keyword

With this setup.cfg snippet, which assertion correctly verifies that only tests marked with 'slow' run when using pytest -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 assert 'skipped' in result.stdout

B assert 'test_fast' in result.stdout and 'test_slow' not in result.stdout

C assert 'collected 2 items' in result.stdout

D assert 'test_slow' in result.stdout and 'test_fast' not in result.stdout

💡 Hint

Using -m slow runs only tests with the slow marker.

The command pytest -m slow runs only tests marked 'slow', so output should show test_slow but not test_fast.

🔧 Debug

advanced

Why does pytest warn about unknown marker despite setup.cfg?

You have this setup.cfg: [pytest] markers = regression: marks regression tests But running tests marked with @pytest.mark.regression still shows a warning about unknown marker. What is the most likely cause?

A The <code>setup.cfg</code> file is not in the root directory where pytest is run.

B The marker name in the test code is misspelled as 'regresion'.

C pytest requires markers to be declared in <code>pytest.ini</code>, not <code>setup.cfg</code>.

D The test function is missing the <code>@pytest.mark.usefixtures</code> decorator.

💡 Hint

pytest reads setup.cfg only if it is in the current directory or above.

If setup.cfg is not in the directory pytest runs from or above, pytest won't find the marker declarations and warns about unknown markers.

❓ framework

advanced

Configuring pytest to ignore warnings via setup.cfg

Which setup.cfg snippet correctly configures pytest to ignore DeprecationWarning during test runs?

A

[pytest]
filterwarnings = ignore::DeprecationWarning

B

[pytest]
ignore_warnings = DeprecationWarning

C

[pytest]
filterwarnings = error::DeprecationWarning

D

[pytest]
warnings_ignore = DeprecationWarning

💡 Hint

pytest uses filterwarnings option with ignore action.

The correct syntax is 'filterwarnings = ignore::DeprecationWarning' to suppress those warnings.

🧠 Conceptual

expert

Effect of testpaths in setup.cfg on test discovery

Given this setup.cfg: [pytest] testpaths = tests integration What is the effect of this configuration when running pytest without arguments?

A pytest will discover tests in all directories except 'tests' and 'integration'.

B pytest will only discover tests inside the 'tests' and 'integration' directories.

C pytest will ignore the 'tests' and 'integration' directories and discover tests elsewhere.

D pytest will run tests only in the current directory, ignoring subdirectories.

💡 Hint

testpaths limits where pytest looks for tests.

The testpaths option tells pytest to look only in the specified directories for tests.