@pytest.mark.skipif with condition

Introduction

Sometimes, you want to skip a test only when a certain condition is true. This helps avoid running tests that don't make sense in some situations.

Skip a test if a required package is not installed.

Skip a test on a specific operating system like Windows or Linux.

Skip a test if a certain environment variable is missing.

Skip a test when running on a slow or limited resource machine.

Syntax

PyTest

@pytest.mark.skipif(condition, reason="explanation")
def test_function():
    # test code here

The condition is a Python expression that returns True or False.

The reason explains why the test is skipped and shows in the test report.

Examples

Skip the test if the OS does not support the fork function.

PyTest

import os
import pytest

@pytest.mark.skipif(not hasattr(os, 'fork'), reason="No fork support on this OS")
def test_fork():
    pass

Skip the test when running on Windows.

PyTest

import sys
import pytest

@pytest.mark.skipif(sys.platform == 'win32', reason="Test not supported on Windows")
def test_unix_only():
    pass

Skip the test if the environment variable MY_ENV is not set.

PyTest

import os
import pytest

@pytest.mark.skipif('MY_ENV' not in os.environ, reason="Environment variable MY_ENV missing")
def test_env_var():
    pass

Sample Program

This script has two tests. One skips on Windows, the other runs only on Windows. When you run it, one test will be skipped depending on your OS.

PyTest

import pytest
import sys

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

@pytest.mark.skipif(sys.platform != 'win32', reason="Run only on Windows")
def test_only_on_windows():
    assert True

if __name__ == '__main__':
    pytest.main(['-v', __file__])

Important Notes

Always provide a clear reason so others understand why the test is skipped.

The condition is evaluated when pytest collects tests, not when tests run.

Use skipif to keep your test suite clean and avoid false failures.

Summary

@pytest.mark.skipif skips tests based on a condition.

Use it to avoid running tests in unsuitable environments.

Always give a reason to explain the skip.

Practice

1. What is the main purpose of using @pytest.mark.skipif in a test?

easy

A. To skip a test when a specific condition is true

B. To run a test multiple times

C. To mark a test as expected to fail

D. To automatically fix test failures

Solution

1. Step 1: Understand the decorator purpose

   @pytest.mark.skipif is used to skip tests conditionally.

2. Step 2: Identify the correct use case

   It skips tests only if the given condition evaluates to True, preventing unsuitable test runs.

3. Final Answer:

   To skip a test when a specific condition is true -> Option A

4. Quick Check:

   Skip test if condition true [OK]

Hint: Skip tests only when condition is true [OK]

Common Mistakes:

• Confusing skipif with parametrize
• Using skipif without a condition
• Thinking skipif runs tests multiple times

2. Which of the following is the correct syntax to skip a test if Python version is less than 3.8?

easy

A. @pytest.mark.skipif(sys.version_info < (3, 8), reason='Python < 3.8')

B. @pytest.skipif(sys.version_info < (3, 8), reason='Python < 3.8')

C. @pytest.mark.skipif(sys.version < 3.8, reason='Python < 3.8')

D. @pytest.mark.skipif(sys.version_info <= 3.8, reason='Python < 3.8')

Solution

1. Step 1: Check correct decorator usage

   The correct decorator is @pytest.mark.skipif, not @pytest.skipif.

2. Step 2: Verify condition and syntax

   Python version is checked with sys.version_info tuple; comparison uses < (less than) and tuple format (3, 8).

3. Final Answer:

   @pytest.mark.skipif(sys.version_info < (3, 8), reason='Python < 3.8') -> Option A

4. Quick Check:

   Correct decorator and version tuple [OK]

Hint: Use sys.version_info tuple with @pytest.mark.skipif [OK]

Common Mistakes:

• Using @pytest.skipif instead of @pytest.mark.skipif
• Comparing sys.version instead of sys.version_info
• Using <= instead of < for version check

3. Given the code below, what will happen when running the test on a Windows system?

import sys
import pytest

@pytest.mark.skipif(sys.platform != 'win32', reason='Only runs on Windows')
def test_windows_feature():
    assert True

medium

A. The test will raise a syntax error

B. The test will always run regardless of platform

C. The test will fail on Windows systems

D. The test will be skipped on non-Windows systems

Solution

1. Step 1: Analyze the skip condition

   The condition sys.platform != 'win32' means skip if platform is not Windows.

2. Step 2: Determine behavior on Windows

   On Windows, sys.platform == 'win32', so condition is False, test runs. On other OS, condition True, test skipped.

3. Final Answer:

   The test will be skipped on non-Windows systems -> Option D

4. Quick Check:

   Skip if not Windows [OK]

Hint: Condition True means skip; False means run test [OK]

Common Mistakes:

• Thinking test runs only on non-Windows
• Confusing != with == in condition
• Assuming syntax error from decorator

4. Identify the error in the following pytest code snippet:

import pytest

@pytest.mark.skipif(reason='No condition provided')
def test_example():
    assert True

medium

A. Reason argument should be outside skipif

B. Incorrect import statement for pytest

C. Missing condition argument in skipif decorator

D. Missing assert statement in test

Solution

1. Step 1: Check skipif decorator usage

   @pytest.mark.skipif requires a condition argument to decide when to skip.

2. Step 2: Identify missing condition

   Here, only reason is provided, no condition, so syntax is invalid.

3. Final Answer:

   Missing condition argument in skipif decorator -> Option C

4. Quick Check:

   skipif needs condition argument [OK]

Hint: Always provide condition before reason in skipif [OK]

Common Mistakes:

• Omitting the condition argument
• Placing reason before condition
• Confusing skipif with skip

5. You want to skip a test only if the environment variable TEST_ENV is set to production. Which of the following is the correct way to write this using @pytest.mark.skipif?

hard

A. @pytest.mark.skipif(os.environ['TEST_ENV'] == 'production', reason='Skip in production')

B. @pytest.mark.skipif(os.getenv('TEST_ENV') == 'production', reason='Skip in production')

C. @pytest.mark.skipif('TEST_ENV' == 'production', reason='Skip in production')

D. @pytest.mark.skipif(os.getenv('TEST_ENV') != 'production', reason='Skip in production')

Solution

1. Step 1: Understand environment variable access

   Use os.getenv('TEST_ENV') to safely get the variable; it returns None if not set.

2. Step 2: Write correct skip condition

   Skip only if value equals 'production', so condition is os.getenv('TEST_ENV') == 'production'.

3. Step 3: Check other options

   @pytest.mark.skipif('TEST_ENV' == 'production', reason='Skip in production') compares string literals, not env variable. @pytest.mark.skipif(os.environ['TEST_ENV'] == 'production', reason='Skip in production') may raise KeyError if variable missing. @pytest.mark.skipif(os.getenv('TEST_ENV') != 'production', reason='Skip in production') skips when not production, opposite of requirement.

4. Final Answer:

   @pytest.mark.skipif(os.getenv('TEST_ENV') == 'production', reason='Skip in production') -> Option B

5. Quick Check:

   Use os.getenv and == 'production' for skipif [OK]

Hint: Use os.getenv for safe env check in skipif [OK]

Common Mistakes:

• Using os.environ without handling missing keys
• Comparing strings directly instead of env variable
• Reversing the skip condition logic