Testpaths configuration helps pytest find your test files easily. It tells pytest where to look for tests.
Testpaths configuration in PyTest
[pytest] testpaths = folder1 folder2
This goes in a pytest.ini file in your project root.
List folders separated by spaces where your test files are located.
[pytest] testpaths = tests
[pytest] testpaths = tests integration_tests
[pytest] testpaths = src/tests
This example shows a pytest.ini file with testpaths set to 'tests'. Pytest will only look inside the 'tests' folder for test files.
The sample test file has two simple tests that both pass.
Running pytest will find and run these tests successfully.
[pytest] testpaths = tests # Folder structure: # project_root/ # ├── pytest.ini # ├── tests/ # │ └── test_sample.py # Content of tests/test_sample.py: import pytest def test_add(): assert 1 + 1 == 2 def test_subtract(): assert 5 - 3 == 2 # Run command: # pytest # Expected output: # ============================= test session starts ============================= # collected 2 items # # tests/test_sample.py .. [100%] # # ============================== 2 passed in 0.01s ==============================
Make sure the folders listed in testpaths actually exist, or pytest will find no tests.
Test files should be named starting with test_ or ending with _test.py for pytest to recognize them.
You can combine testpaths with other pytest.ini settings like python_files to customize test discovery.
Testpaths configuration tells pytest where to find your test files.
It helps organize tests and speeds up test discovery.
Set it in pytest.ini by listing folders with tests.
Practice
testpaths setting in a pytest.ini file?Solution
Step 1: Understand the role of
Thetestpathstestpathssetting tells pytest where to find test files by listing directories.Step 2: Compare with other options
Other options like test order, timeout, or report format are configured differently, not withtestpaths.Final Answer:
To specify which folders pytest should look in for test files -> Option BQuick Check:
testpaths = test folders [OK]
- Confusing testpaths with test order settings
- Thinking testpaths sets test timeouts
- Assuming testpaths changes report style
testpaths in pytest.ini to look in folders tests and integration?Solution
Step 1: Check pytest.ini syntax for testpaths
Inpytest.ini,testpathslists folders separated by spaces without quotes or commas.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.Final Answer:
[pytest] testpaths = tests integration -> Option AQuick Check:
Space-separated folder names, no quotes [OK]
- Using commas instead of spaces
- Adding quotes or brackets around folder names
- Placing testpaths outside [pytest] section
pytest.ini content:[pytest] testpaths = tests integration
And this folder structure:
project/
tests/
test_alpha.py
integration/
test_beta.py
docs/
test_docs.pyWhich test files will pytest discover and run?
Solution
Step 1: Identify folders listed in testpaths
Thetestpathssetting includestestsandintegrationfolders only.Step 2: Match test files in those folders
Filestest_alpha.pyintestsandtest_beta.pyinintegrationwill be found.test_docs.pyis indocs, which is not listed.Final Answer:
test_alpha.py and test_beta.py only -> Option DQuick Check:
Only testpaths folders' tests run [OK]
- Assuming all test files in project run
- Including tests from folders not in testpaths
- Confusing folder names with test file names
testpaths = tests in pytest.ini but pytest still discovers tests in other folders. What is the most likely cause?Solution
Step 1: Understand pytest config precedence
pytest can read multiple config files liketox.iniorsetup.cfgthat may overridepytest.ini.Step 2: Check for conflicting configs
If tests outsidetestsrun, likely another config file sets differenttestpathsor disables it.Final Answer:
There is another config file overriding testpaths -> Option AQuick Check:
Multiple configs can override testpaths [OK]
- Assuming pytest.ini changes apply without reload
- Thinking testpaths filters test names only
- Believing pytest ignores testpaths by default
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?Solution
Step 1: Use testpaths to include desired folders
Settestpaths = unit_tests api_teststo include both folders.Step 2: Exclude the slow subfolder with norecursedirs
Usenorecursedirs = api_tests/slowto prevent pytest from searching inside that subfolder.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 usesignorewhich is not a valid pytest.ini setting.Final Answer:
[pytest] testpaths = unit_tests api_tests norecursedirs = api_tests/slow -> Option CQuick Check:
Include folders with testpaths, exclude subfolders with norecursedirs [OK]
- Including excluded folders in testpaths
- Using invalid config keys like ignore
- Excluding whole folders instead of subfolders
Ready to prove it?
Pass the test and this pattern moves unknown
