Built-in markers (skip, skipif, xfail) in PyTest - Build an Automation Script

Automate tests using pytest built-in markers skip, skipif, and xfail

Preconditions (2)

Step 1: Create a test function test_always_skip that is marked to always skip

Step 2: Create a test function test_skip_if_python_version that skips if Python version is less than 3.8

Step 3: Create a test function test_expected_failure that is marked as expected to fail

Step 4: Run pytest on the test file

Step 5: Observe the test results for skip, skipif, and xfail markers

✅ Expected Result: test_always_skip is skipped unconditionally, test_skip_if_python_version is skipped only if Python version < 3.8, test_expected_failure is reported as expected failure (xfail)

Automation Requirements - pytest

Assertions Needed:

Verify test_always_skip is skipped

Verify test_skip_if_python_version is skipped conditionally

Verify test_expected_failure is marked as xfail

Best Practices:

Use pytest.mark.skip with reason

Use pytest.mark.skipif with a clear condition and reason

Use pytest.mark.xfail with reason

Keep test functions simple and focused

Run tests with -rs option to show skip reasons

Automated Solution

PyTest

import sys
import pytest

@pytest.mark.skip(reason="Skipping this test always")
def test_always_skip():
    assert True

@pytest.mark.skipif(sys.version_info < (3, 8), reason="Requires Python 3.8 or higher")
def test_skip_if_python_version():
    assert True

@pytest.mark.xfail(reason="This test is expected to fail")
def test_expected_failure():
    assert 1 == 2

This script uses pytest built-in markers to control test execution.

test_always_skip is marked with @pytest.mark.skip so it will always be skipped. The reason is provided for clarity in reports.

test_skip_if_python_version uses @pytest.mark.skipif with a condition that checks if the Python version is less than 3.8. It will skip only if this condition is true.

test_expected_failure is marked with @pytest.mark.xfail because it is expected to fail. Pytest will report it as an expected failure, not a test failure.

This approach helps manage tests that should not run under certain conditions or are known to fail temporarily.

Common Mistakes - 3 Pitfalls

Not providing a reason for skip or xfail markers

Using skip instead of skipif for conditional skipping

Marking a test as xfail without a failing assertion

Bonus Challenge

Now add data-driven testing with skipif marker to skip tests for specific input values

Show Hint