pytest.ini configuration - Build an Automation Script

Configure pytest.ini to set test markers and default options

Preconditions (2)

Step 1: Create a pytest.ini file in the project root directory

Step 2: Add a marker named 'smoke' with a description

Step 3: Set the default command line option to show detailed test output (-v)

Step 4: Run pytest without any command line arguments

Step 5: Verify that tests run with verbose output

Step 6: Verify that the 'smoke' marker is recognized by pytest

✅ Expected Result: pytest runs tests with verbose output by default and recognizes the 'smoke' marker without errors

Automation Requirements - pytest

Assertions Needed:

Verify pytest runs with verbose output by default

Verify pytest recognizes the 'smoke' marker without warnings

Best Practices:

Use a pytest.ini file in the root directory for configuration

Define markers under [pytest] section with clear descriptions

Avoid hardcoding command line options in test scripts

Use pytest's built-in capabilities to check for warnings

Automated Solution

PyTest

[pytest]
markers =
    smoke: mark a test as a smoke test
addopts = -v

# test_sample.py
import pytest

@pytest.mark.smoke
def test_example():
    assert 1 + 1 == 2

# test_pytest_ini.py
import subprocess
import sys
import re

def test_pytest_ini_configuration():
    # Run pytest in the current directory without extra args
    result = subprocess.run([sys.executable, '-m', 'pytest'], capture_output=True, text=True)
    output = result.stdout + result.stderr

    # Check verbose output: look for 'test_example' in output and '-v' effect (e.g., test names shown)
    assert 'test_example' in output
    assert re.search(r'collected \d+ items', output)

    # Check no warnings about unknown markers
    assert 'PytestUnknownMarkWarning' not in output
    assert 'WARNING' not in output or 'smoke' in output

The pytest.ini file sets the smoke marker and adds -v to addopts for verbose output by default.

The test_sample.py file contains a simple test marked with @pytest.mark.smoke.

The automation script test_pytest_ini.py runs pytest as a subprocess without extra arguments to verify the configuration.

It asserts that the test name appears in the output, indicating verbose mode is active.

It also checks that no warnings about unknown markers appear, confirming the marker is recognized.

This approach tests the pytest.ini configuration end-to-end without modifying test runner commands.

Common Mistakes - 4 Pitfalls

{'mistake': 'Not placing pytest.ini in the project root directory', 'why_bad': "pytest will not find the configuration file and default options or markers won't be applied", 'correct_approach': 'Always place pytest.ini in the root directory where pytest is run'}

Defining markers without descriptions or under wrong section

Hardcoding command line options in test scripts instead of pytest.ini

Ignoring warnings about unknown markers during test runs

Bonus Challenge

Now add a second marker named 'regression' and verify both markers are recognized without warnings

Show Hint

Practice

1. What is the primary purpose of the pytest.ini file in a pytest project?

easy

A. To install pytest dependencies automatically

B. To store configuration settings for pytest test runs

C. To write test functions and test cases

D. To generate test reports after running tests

Solution

1. Step 1: Understand pytest.ini role

   The pytest.ini file is used to configure pytest behavior before running tests.

2. Step 2: Differentiate from other files

   Test functions are written in Python files, not in pytest.ini. Dependency installation and report generation are handled elsewhere.

3. Final Answer:

   To store configuration settings for pytest test runs -> Option B

4. Quick Check:

   pytest.ini = config file [OK]

Hint: pytest.ini holds settings, not test code or reports [OK]

Common Mistakes:

• Confusing pytest.ini with test script files
• Thinking pytest.ini installs packages
• Assuming pytest.ini generates reports

2. Which of the following is the correct way to set the verbosity level to 2 in pytest.ini?

easy

A. [pytest]
addopts = -vv

B. [pytest]
verbosity = 2

C. [pytest]
verbosity: 2

D. [pytest]
addopts = --verbosity=2

Solution

1. Step 1: Recall pytest verbosity setting

   pytest uses addopts to pass command-line options like -vv for verbosity level 2.

2. Step 2: Check syntax correctness

   [pytest] addopts = -vv correctly uses addopts = -vv. [pytest] verbosity = 2 uses an invalid key verbosity. [pytest] verbosity: 2 uses wrong syntax with colon. [pytest] addopts = --verbosity=2 uses an invalid flag.

3. Final Answer:

   [pytest] addopts = -vv -> Option A

4. Quick Check:

   Verbosity level 2 via addopts = -vv [OK]

Hint: Use addopts with -vv for verbosity level 2 in pytest.ini [OK]

Common Mistakes:

• Using 'verbosity' instead of 'addopts'
• Incorrect syntax with colon instead of equals
• Using unsupported flags like --verbosity

3. Given this pytest.ini content:

[pytest]
markers = slow: marks tests as slow
          smoke: marks smoke tests
addopts = -rs

What will be the effect of running pytest with this configuration?

medium

A. Tests marked as slow or smoke will be skipped automatically

B. pytest will run tests with no output

C. Only tests marked as slow will run

D. pytest will show extra summary info for skipped and failed tests

Solution

1. Step 1: Understand markers and addopts

   The markers section defines labels for tests but does not skip them automatically. The addopts = -rs option tells pytest to show extra summary info for skipped and failed tests.

2. Step 2: Analyze each option

   Tests marked as slow or smoke will be skipped automatically is wrong because markers alone don't skip tests. Only tests marked as slow will run is wrong because no selection is made. pytest will run tests with no output is wrong because -rs increases output detail.

3. Final Answer:

   pytest will show extra summary info for skipped and failed tests -> Option D

4. Quick Check:

   addopts = -rs shows skip/fail summary [OK]

Hint: addopts = -rs shows skip and fail summaries [OK]

Common Mistakes:

• Thinking markers skip tests automatically
• Confusing addopts flags with test selection
• Assuming no output with -rs option

4. You added this to your pytest.ini file:

[pytest]
markers = regression
addopts = --maxfail=3

But when you run pytest, you get an error: ERROR: unknown option: --maxfail=3
What is the most likely cause?

medium

A. The addopts line should use -maxfail=3 instead

B. The pytest.ini file is missing the [pytest] header

C. The pytest version is outdated and does not support --maxfail

D. Markers must be defined after addopts in pytest.ini

Solution

1. Step 1: Understand the error message

   The error says unknown option: --maxfail=3, meaning pytest does not recognize this option.

2. Step 2: Check possible causes

   The addopts line should use -maxfail=3 instead is wrong because --maxfail requires two dashes. The pytest.ini file is missing the [pytest] header is wrong because the header is present. Markers must be defined after addopts in pytest.ini is wrong because order does not matter. The most common cause is an outdated pytest version that lacks support for --maxfail.

3. Final Answer:

   The pytest version is outdated and does not support --maxfail -> Option C

4. Quick Check:

   Unknown option usually means outdated pytest [OK]

Hint: Unknown option often means pytest version too old [OK]

Common Mistakes:

• Changing option syntax incorrectly
• Forgetting to include [pytest] header
• Thinking order of keys matters in pytest.ini

5. You want to configure pytest.ini to:
1. Mark tests with slow and critical labels.
2. Run only tests matching the pattern test_*.py.
3. Stop after 2 failures.

Which of the following pytest.ini configurations achieves all three correctly?

hard

A. [pytest]
markers = slow: slow tests
critical: critical tests
python_files = test_*.py
addopts = --maxfail=2

B. [pytest]
markers = slow
critical
python_files = test_*.py
addopts = -x --maxfail=2

C. [pytest]
markers = slow: slow tests
critical: critical tests
python_files = test_*.py
addopts = -x --maxfail=2

D. [pytest]
markers = slow: slow tests
critical: critical tests
python_files = test_*.py
addopts = --maxfail=2 -x

Solution

1. Step 1: Check markers syntax

   Options A, C, and D correctly define markers with descriptions. [pytest] markers = slow critical python_files = test_*.py addopts = -x --maxfail=2 lacks descriptions, which is allowed but less clear.

2. Step 2: Verify test file pattern

   All options set python_files = test_*.py correctly.

3. Step 3: Confirm failure stop and run options

   [pytest] markers = slow: slow tests critical: critical tests python_files = test_*.py addopts = --maxfail=2 uses addopts = --maxfail=2 which stops after 2 failures but does not stop immediately on first failure. Options C and D add -x which stops after first failure, conflicting with requirement to stop after 2 failures. [pytest] markers = slow critical python_files = test_*.py addopts = -x --maxfail=2 lacks descriptions in markers.

4. Final Answer:

   Markers with descriptions, correct python_files, and stop after 2 failures -> Option A

5. Quick Check:

   Use --maxfail=2 without -x to stop after 2 failures [OK]

Hint: Use --maxfail=2 without -x to stop after 2 failures [OK]

Common Mistakes:

• Adding -x stops after 1 failure, not 2
• Omitting marker descriptions
• Misconfiguring python_files pattern