Why configuration standardizes test behavior in PyTest - Test Execution Impact

Test Overview

This test checks that a pytest configuration file standardizes the test behavior by setting a fixed seed for randomness and a common timeout. It verifies that the test runs consistently with these settings.

Test Code - pytest

PyTest

import pytest
import random

def test_random_number():
    # The seed is set in pytest.ini to ensure consistent random numbers
    num = random.randint(1, 100)
    assert num == 42  # Expected fixed number due to seed

# pytest.ini content:
# [pytest]
# addopts = --timeout=5
# random_seed = 12345

# conftest.py content:
# import random
# def pytest_configure(config):
#     seed = config.getoption('random_seed', default=12345)
#     random.seed(seed)

Execution Trace - 3 Steps

Step	Action	System State	Assertion	Result
1	Test runner starts pytest with configuration loaded from pytest.ini and conftest.py	pytest.ini sets random_seed=12345 and timeout=5 seconds; conftest.py sets random.seed(12345)	—	PASS
2	pytest runs test_random_number function	random.seed is set to 12345, so random.randint(1, 100) returns a fixed number	assert num == 42	PASS
3	Test completes within the configured timeout of 5 seconds	Test finishes quickly without timeout	—	PASS

Failure Scenario

Failing Condition: If the configuration does not set the random seed, the random number will vary and assertion will fail

Execution Trace Quiz - 3 Questions

Why does the test assert that the random number equals 42?

A Because the random seed is set to produce consistent results

B Because 42 is the default random number

C Because the test runs multiple times

D Because pytest ignores randomness

Key Result

Using configuration files like pytest.ini to set common parameters such as random seeds and timeouts helps tests behave consistently and predictably across runs.

Practice

1. Why is using a pytest.ini configuration file important for test behavior?

easy

A. It sets consistent options so tests run the same way every time.

B. It automatically fixes all test failures.

C. It replaces the need to write test functions.

D. It speeds up test execution by skipping all tests.

Solution

1. Step 1: Understand the role of configuration files

   Configuration files like pytest.ini define settings that control how tests run, such as markers, test paths, or warnings.

2. Step 2: Recognize the benefit of standardization

   By setting options in one place, all tests behave consistently across different runs and environments.

3. Final Answer:

   It sets consistent options so tests run the same way every time. -> Option A

4. Quick Check:

   Configuration standardizes test behavior = A [OK]

Hint: Config files keep test runs consistent everywhere [OK]

Common Mistakes:

• Thinking config files fix test code errors automatically
• Believing config files replace writing tests
• Assuming config files skip tests to speed up runs

2. Which of the following is the correct way to specify a marker in pytest.ini to standardize test selection?

easy

A. [pytest]
mark = slow: marks tests as slow

B. [pytest]
markers slow: marks tests as slow

C. [pytest]
markers = slow: marks tests as slow

D. [pytest]
markers = slow marks tests as slow

Solution

1. Step 1: Recall the correct syntax for markers in pytest.ini

   The correct section header is [pytest] and the key is markers with an equals sign and description.

2. Step 2: Identify the properly formatted option

   [pytest] markers = slow: marks tests as slow uses markers = slow: marks tests as slow, which matches pytest documentation syntax.

3. Final Answer:

   [pytest] markers = slow: marks tests as slow -> Option C

4. Quick Check:

   Correct marker syntax = B [OK]

Hint: Markers use 'markers =' under [pytest] section [OK]

Common Mistakes:

• Using 'mark' instead of 'markers'
• Missing equals sign after 'markers'
• Not enclosing section header in brackets

3. Given this pytest.ini content:

[pytest]
addopts = -v --maxfail=2

What will happen when you run pytest on a test suite with 5 failing tests?

medium

A. Pytest will ignore failures and pass all tests.

B. Pytest will run all tests and show minimal output.

C. Pytest will stop after 5 failures and show verbose output.

D. Pytest will stop after 2 failures and show verbose output.

Solution

1. Step 1: Interpret the addopts options

   The option -v means verbose output. The option --maxfail=2 means pytest stops after 2 failures.

2. Step 2: Predict test run behavior

   When running tests with 5 failures, pytest will stop after the second failure and show detailed output because of -v.

3. Final Answer:

   Pytest will stop after 2 failures and show verbose output. -> Option D

4. Quick Check:

   addopts '-v --maxfail=2' = stop at 2 fails + verbose [OK]

Hint: maxfail limits failures; -v shows details [OK]

Common Mistakes:

• Thinking pytest runs all tests despite maxfail
• Confusing verbose with minimal output
• Assuming maxfail=2 means stop after 5 failures

4. You added filterwarnings = ignore::DeprecationWarning in pytest.ini but still see deprecation warnings during test runs. What is the likely cause?

medium

A. You need to add --disable-warnings to the command line instead.

B. The filterwarnings option is misspelled or misplaced in the config file.

C. Deprecation warnings cannot be ignored in pytest.

D. Pytest does not support filtering warnings via configuration.

Solution

1. Step 1: Verify correct spelling and placement of filterwarnings

   The option must be spelled exactly as filterwarnings under the [pytest] section in pytest.ini.

2. Step 2: Understand pytest's support for warning filters

   Pytest supports filtering warnings via config. If warnings still appear, likely the option is misspelled or in wrong section.

3. Final Answer:

   The filterwarnings option is misspelled or misplaced in the config file. -> Option B

4. Quick Check:

   Correct spelling and placement = D [OK]

Hint: Check spelling and section for config options [OK]

Common Mistakes:

• Assuming pytest ignores config filters
• Using wrong option names
• Not placing options under [pytest] section

5. You want to ensure all tests marked @pytest.mark.slow are skipped by default unless explicitly included. Which pytest.ini configuration achieves this standardized behavior?

hard

A. [pytest]
markers = slow: marks slow tests
addopts = -m 'not slow'

B. [pytest]
markers = slow: marks slow tests
addopts = -m slow

C. [pytest]
markers = slow: marks slow tests
addopts = --skip slow

D. [pytest]
markers = slow: marks slow tests
addopts = --disable slow

Solution

1. Step 1: Understand marker usage and addopts filtering

   To skip tests marked slow by default, use -m 'not slow' to run tests not marked slow.

2. Step 2: Identify correct addopts syntax

   [pytest] markers = slow: marks slow tests addopts = -m 'not slow' uses addopts = -m 'not slow', which tells pytest to exclude slow tests unless overridden.

3. Final Answer:

   [pytest] markers = slow: marks slow tests addopts = -m 'not slow' -> Option A

4. Quick Check:

   Exclude slow tests by default = C [OK]

Hint: Use '-m not marker' to skip marked tests by default [OK]

Common Mistakes:

• Using '-m slow' runs only slow tests, not skips them
• Trying unsupported options like --skip or --disable
• Not defining the marker in pytest.ini