Testpaths configuration in PyTest - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the testpaths in pytest configuration.

PyTest

[pytest]
testpaths = [1]

Drag options to blanks, or click blank then click option'

Adocs

Bsrc

Ctests

Dsetup.py

Attempts:

3 left

💡 Hint

Common Mistakes

Using source code folder instead of test folder

Using a file name instead of a folder

The testpaths option tells pytest where to look for tests. Usually, tests are in the tests folder.

2fill in blank

medium

Complete the pytest configuration to include multiple testpaths.

PyTest

[pytest]
testpaths = [1]

Drag options to blanks, or click blank then click option'

Adocs tests

Btests integration_tests

Csrc tests

Dsetup.py tests

Attempts:

3 left

💡 Hint

Common Mistakes

Using commas instead of spaces

Including non-test folders

You can specify multiple folders separated by spaces in testpaths to tell pytest to look in both places.

3fill in blank

hard

Fix the error in the pytest configuration to correctly specify testpaths.

PyTest

[pytest]
testpaths = [1]

Drag options to blanks, or click blank then click option'

Atests integration_tests

Btests,integration_tests

Ctests,integration_tests,

Dtests;integration_tests

Attempts:

3 left

💡 Hint

Common Mistakes

Using commas or semicolons to separate folders

Adding trailing commas

Pytest expects testpaths as space-separated folder names, not comma or semicolon separated.

4fill in blank

hard

Fill both blanks to configure pytest to look for tests in the 'tests' folder and specify the pattern for test files.

PyTest

[pytest]
testpaths = [1]
python_files = [2]

Drag options to blanks, or click blank then click option'

Atests

Bsrc

Ctest_*.py

Dcheck_*.py

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong folder name

Using incorrect file pattern

The testpaths option sets the folders to search. The python_files option sets the pattern pytest looks for in test files, usually test_*.py.

5fill in blank

hard

Fill all three blanks to configure pytest to look in 'tests' and 'integration_tests' folders, use 'test_*.py' pattern for files, and 'Test*' prefix for test classes.

PyTest

[pytest]
testpaths = [1]
python_files = [2]
python_classes = [3]

Drag options to blanks, or click blank then click option'

Atests integration_tests

Btest_*.py

CTest*

Dcheck_*

Attempts:

3 left

💡 Hint

Common Mistakes

Using commas instead of spaces for folders

Missing * wildcard in patterns

This configuration tells pytest to look in both folders, find test files matching test_*.py, and test classes starting with Test.

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