What if you could run only the tests you need with one simple setting?
Why Testpaths configuration in PyTest? - Purpose & Use Cases
Imagine you have a big project with many test files scattered in different folders. You want to run only tests from a specific folder, but you have to manually pick each test file every time.
Manually selecting test files is slow and easy to forget. You might run tests from the wrong folder or miss some important tests. This wastes time and causes confusion.
Testpaths configuration lets you tell pytest exactly which folders to look in for tests. This way, pytest automatically finds and runs only the tests you want, saving you time and avoiding mistakes.
pytest tests/test_example.py tests/other/test_sample.py
[pytest] testpaths = tests
It enables fast, focused test runs by automatically selecting the right test folders every time.
When working on a feature in the 'tests/login' folder, you can configure testpaths to run only those tests, so you get quick feedback without running unrelated tests.
Manually picking test files is slow and error-prone.
Testpaths configuration tells pytest where to find tests automatically.
This makes running tests faster and more reliable.
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
