@pytest.mark.skipif with condition - Framework Patterns

Framework Mode - @pytest.mark.skipif with condition

Folder Structure

project-root/
├── tests/
│   ├── test_example.py
│   ├── test_feature_a.py
│   └── test_feature_b.py
├── conftest.py
├── pytest.ini
└── utils/
    └── helpers.py
  

This is a typical Pytest project structure. Tests live in the tests/ folder. Shared helpers go in utils/. Configuration files like pytest.ini and conftest.py help manage test setup.

Test Framework Layers

• Test Cases: Actual test functions inside tests/ folder, e.g., test_example.py.
• Fixtures & Setup: In conftest.py, reusable setup code and test data.
• Utilities: Helper functions in utils/helpers.py for common tasks.
• Configuration: pytest.ini for test options and markers.

The @pytest.mark.skipif decorator is used in test cases to skip tests based on conditions like environment or Python version.

Configuration Patterns

Use pytest.ini to register custom markers and set default options:

[pytest]
markers =
    skipif: skip test if condition is true
  

Use environment variables or Python's sys module to create skip conditions. For example, skip tests on Windows or when a package is missing.

Example skip condition in test:

import sys
import pytest

@pytest.mark.skipif(sys.platform == "win32", reason="Does not run on Windows")
def test_not_on_windows():
    assert True
  

Test Reporting and CI/CD Integration

Pytest outputs clear pass/fail results in the console. When tests are skipped by @pytest.mark.skipif, the report shows s for skipped tests.

Integrate with CI/CD tools (GitHub Actions, Jenkins) to run tests automatically. Skipped tests are reported but do not fail the build.

Use plugins like pytest-html to generate detailed HTML reports showing skipped tests with reasons.

Best Practices

• Always provide a clear reason string in @pytest.mark.skipif to explain why the test is skipped.
• Use simple, deterministic conditions for skipping to avoid flaky test runs.
• Register custom markers in pytest.ini to avoid warnings and keep tests organized.
• Keep skip conditions relevant to environment or dependencies, not test logic.
• Use skipif to handle platform differences, missing packages, or feature flags gracefully.

Self Check

Question: Where in this framework structure would you add a new test that should be skipped on Python versions below 3.8?

Answer: Add the test function inside the tests/ folder (e.g., tests/test_example.py) and decorate it with @pytest.mark.skipif using a condition that checks sys.version_info.

Key Result

Use @pytest.mark.skipif with clear conditions and reasons to skip tests based on environment or dependencies.