Testpaths configuration in PyTest - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of pytest testpaths effect

Given the pytest configuration below, what tests will pytest discover and run?

PyTest

[pytest]
testpaths = tests/integration

# Directory structure:
# tests/
# ├── integration/
# │   └── test_api.py
# └── unit/
#     └── test_utils.py

# Both test_api.py and test_utils.py contain valid test functions.

A No tests will run because testpaths is misconfigured.

B Both tests/integration/test_api.py and tests/unit/test_utils.py will run.

C Only tests in tests/integration/test_api.py will run.

D Only tests in tests/unit/test_utils.py will run.

💡 Hint

The testpaths setting limits pytest to look only inside specified directories.

The testpaths option tells pytest to only look for tests inside the specified directory 'tests/integration'. Therefore, tests in 'tests/unit' are ignored.

❓ assertion

intermediate

Assertion to verify testpaths filtering

You want to write a pytest test that verifies pytest only collects tests from the 'tests/functional' directory as set in testpaths. Which assertion correctly checks this behavior?

PyTest

import pytest

collected = pytest.main(['--collect-only'])
# Assume collected_tests is a list of test node ids collected by pytest

A assert 'tests/functional' not in collected_tests

B assert any('tests/functional' in test for test in collected_tests)

C assert all('tests/unit' in test for test in collected_tests)

D assert all('tests/functional' in test for test in collected_tests)

💡 Hint

To confirm filtering, all collected tests should be inside the specified directory.

Using all() ensures every collected test path includes 'tests/functional', confirming pytest only collected tests from that directory.

🔧 Debug

advanced

Why are tests outside testpaths not running?

You configured pytest with testpaths = ['tests/api'] but tests in 'tests/api' and 'tests/db' exist. Only tests in 'tests/api' run. You want tests in both directories to run. What is the cause?

PyTest

[pytest]
testpaths = tests/api

A testpaths restricts pytest to only the specified directory; 'tests/db' is excluded because it is not listed.

B testpaths only accepts one directory; multiple directories must be comma-separated in one string.

C pytest ignores testpaths if multiple test directories exist.

D testpaths must be set in pytest.ini, not in pyproject.toml.

💡 Hint

Check how testpaths limits test discovery.

The testpaths option limits pytest to only look inside the specified directories. Since 'tests/db' is not listed, its tests are not discovered or run.

❓ framework

advanced

Configuring multiple testpaths in pytest.ini

How should you correctly configure pytest.ini to include both 'tests/unit' and 'tests/integration' directories in testpaths?

A

[pytest]
testpaths = tests/unit, tests/integration

B

[pytest]
testpaths =
    tests/unit
    tests/integration

C

[pytest]
testpaths = tests/unit tests/integration

D

[pytest]
testpaths = ['tests/unit', 'tests/integration']

💡 Hint

Check pytest.ini syntax for multi-line values.

pytest.ini supports multi-line values for options. Listing each directory on its own indented line under testpaths is the correct way to specify multiple paths.

🧠 Conceptual

expert

Effect of testpaths on pytest test collection order

Which statement about the effect of the testpaths configuration on pytest test collection order is true?

A testpaths only filters directories but does not guarantee the order in which tests are collected or run.

B testpaths causes pytest to run tests in alphabetical order regardless of directory order.

C testpaths enforces tests to run in the order directories are listed.

D testpaths disables test collection order and runs tests randomly.

💡 Hint

Consider what testpaths controls versus test order.

testpaths limits where pytest looks for tests but does not control the order of test collection or execution. Test order is controlled by other pytest options or plugins.

Practice

1. What is the main purpose of the testpaths setting in a pytest.ini file?

easy

A. To configure the test report format

B. To specify which folders pytest should look in for test files

C. To set the timeout for each test

D. To define the order in which tests run

Solution

1. Step 1: Understand the role of testpaths

   The testpaths setting tells pytest where to find test files by listing directories.

2. Step 2: Compare with other options

   Other options like test order, timeout, or report format are configured differently, not with testpaths.

3. Final Answer:

   To specify which folders pytest should look in for test files -> Option B

4. Quick Check:

   testpaths = test folders [OK]

Hint: testpaths lists folders to find tests [OK]

Common Mistakes:

• Confusing testpaths with test order settings
• Thinking testpaths sets test timeouts
• Assuming testpaths changes report style

2. Which of the following is the correct syntax to set testpaths in pytest.ini to look in folders tests and integration?

easy

A. [pytest]
testpaths = tests integration

B. [pytest]
testpaths = ['tests', 'integration']

C. [pytest]
testpaths = tests,integration

D. [pytest]
testpaths = "tests integration"

Solution

1. Step 1: Check pytest.ini syntax for testpaths

   In pytest.ini, testpaths lists folders separated by spaces without quotes or commas.

2. Step 2: Validate each option

   [pytest] testpaths = tests integration uses space-separated folder names correctly. Options A and D use quotes or brackets incorrectly. [pytest] testpaths = tests,integration uses commas which pytest does not accept here.

3. Final Answer:

   [pytest] testpaths = tests integration -> Option A

4. Quick Check:

   Space-separated folder names, no quotes [OK]

Hint: Use space-separated folder names without quotes [OK]

Common Mistakes:

• Using commas instead of spaces
• Adding quotes or brackets around folder names
• Placing testpaths outside [pytest] section

3. Given this pytest.ini content:

[pytest]
testpaths = tests integration

And this folder structure:

project/
  tests/
    test_alpha.py
  integration/
    test_beta.py
  docs/
    test_docs.py

Which test files will pytest discover and run?

medium

A. Only test_docs.py

B. test_alpha.py, test_beta.py, and test_docs.py

C. Only test_alpha.py

D. test_alpha.py and test_beta.py only

Solution

1. Step 1: Identify folders listed in testpaths

   The testpaths setting includes tests and integration folders only.

2. Step 2: Match test files in those folders

   Files test_alpha.py in tests and test_beta.py in integration will be found. test_docs.py is in docs, which is not listed.

3. Final Answer:

   test_alpha.py and test_beta.py only -> Option D

4. Quick Check:

   Only testpaths folders' tests run [OK]

Hint: Only tests in testpaths folders run [OK]

Common Mistakes:

• Assuming all test files in project run
• Including tests from folders not in testpaths
• Confusing folder names with test file names

4. You set testpaths = tests in pytest.ini but pytest still discovers tests in other folders. What is the most likely cause?

medium

A. There is another config file overriding testpaths

B. You forgot to restart pytest after editing pytest.ini

C. testpaths only filters test names, not folders

D. pytest ignores testpaths by default

Solution

1. Step 1: Understand pytest config precedence

   pytest can read multiple config files like tox.ini or setup.cfg that may override pytest.ini.

2. Step 2: Check for conflicting configs

   If tests outside tests run, likely another config file sets different testpaths or disables it.

3. Final Answer:

   There is another config file overriding testpaths -> Option A

4. Quick Check:

   Multiple configs can override testpaths [OK]

Hint: Check for multiple config files overriding settings [OK]

Common Mistakes:

• Assuming pytest.ini changes apply without reload
• Thinking testpaths filters test names only
• Believing pytest ignores testpaths by default

5. You want pytest to only run tests in unit_tests and api_tests folders, but exclude api_tests/slow. How can you configure pytest.ini using testpaths and other settings to achieve this?

hard

A. [pytest]
testpaths = unit_tests
norecursedirs = api_tests/slow

B. [pytest]
testpaths = unit_tests api_tests/slow
norecursedirs = api_tests

C. [pytest]
testpaths = unit_tests api_tests
norecursedirs = api_tests/slow

D. [pytest]
testpaths = unit_tests api_tests
ignore = api_tests/slow

Solution

1. Step 1: Use testpaths to include desired folders

   Set testpaths = unit_tests api_tests to include both folders.

2. Step 2: Exclude the slow subfolder with norecursedirs

   Use norecursedirs = api_tests/slow to prevent pytest from searching inside that subfolder.

3. Step 3: Verify other options are incorrect

   [pytest] testpaths = unit_tests api_tests/slow norecursedirs = api_tests includes the slow folder in testpaths, which is wrong. [pytest] testpaths = unit_tests norecursedirs = api_tests/slow excludes api_tests entirely. [pytest] testpaths = unit_tests api_tests ignore = api_tests/slow uses ignore which is not a valid pytest.ini setting.

4. Final Answer:

   [pytest] testpaths = unit_tests api_tests norecursedirs = api_tests/slow -> Option C

5. Quick Check:

   Include folders with testpaths, exclude subfolders with norecursedirs [OK]

Hint: Use testpaths to include, norecursedirs to exclude subfolders [OK]

Common Mistakes:

• Including excluded folders in testpaths
• Using invalid config keys like ignore
• Excluding whole folders instead of subfolders