@pytest.mark.skipif with condition - Build an Automation Script

Automate test skipping with @pytest.mark.skipif based on Python version

Preconditions (2)

Step 1: Create a test function decorated with @pytest.mark.skipif

Step 2: Set the skip condition to skip the test if Python version is less than 3.12

Step 3: Inside the test, assert that 1 + 1 equals 2

Step 4: Run the test using pytest

Step 5: Verify that the test is skipped if Python version is less than 3.12

Step 6: Verify that the test runs and passes if Python version is 3.12 or higher

✅ Expected Result: Test is skipped on Python versions below 3.12 and runs successfully on Python 3.12 or higher

Automation Requirements - pytest

Assertions Needed:

Assert 1 + 1 == 2 inside the test

Verify test is skipped or run based on Python version condition

Best Practices:

Use @pytest.mark.skipif with a clear and correct condition

Use sys.version_info for version checking

Keep test function simple and focused

Run tests with pytest CLI to see skip reports

Automated Solution

PyTest

import sys
import pytest

@pytest.mark.skipif(sys.version_info < (3, 12), reason="Requires Python 3.12 or higher")
def test_addition():
    assert 1 + 1 == 2

if __name__ == "__main__":
    import pytest
    pytest.main([__file__])

This script imports sys and pytest. The test function test_addition is decorated with @pytest.mark.skipif that checks if the Python version is less than 3.12. If true, pytest will skip this test and show the reason.

The test itself is simple: it asserts that 1 + 1 equals 2.

Running this script with pytest will skip the test on Python versions below 3.12 and run it on 3.12 or higher, showing a pass result.

Common Mistakes - 3 Pitfalls

Using a string instead of a boolean expression in skipif condition

Not providing a reason parameter in @pytest.mark.skipif

Checking Python version with sys.version instead of sys.version_info

Bonus Challenge

Now add multiple skip conditions to skip the test if Python version is less than 3.12 or if an environment variable 'SKIP_TEST' is set to 'true'

Show Hint

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