Project structure for tests in PyTest - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to name the folder where pytest looks for test files by default.

PyTest

The default folder for pytest test files is named '[1]'.

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

Atests

Bsrc

Cdocs

Dbin

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'src' or 'bin' as the test folder name.

Naming the folder 'test' instead of 'tests'.

Pytest by default looks for test files inside a folder named tests.

2fill in blank

medium

Complete the code to name the prefix pytest expects for test files.

PyTest

Pytest looks for test files starting with '[1]'.

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

Acheck_

Bspec_

Crun_

Dtest_

Attempts:

3 left

💡 Hint

Common Mistakes

Using prefixes like 'check_' or 'run_' which pytest does not recognize by default.

Pytest expects test files to start with test_ to identify them as test scripts.

3fill in blank

hard

Fix the error in the test file naming to make pytest recognize it.

PyTest

Rename the file from 'exampleTests.py' to '[1].py' to follow pytest conventions.

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

Atest_example

Bexample_test

CTests_example

Dexampletests

Attempts:

3 left

💡 Hint

Common Mistakes

Using uppercase letters in the prefix.

Placing 'test' at the end instead of the start.

Pytest requires test files to start with test_. So test_example.py is correct.

4fill in blank

hard

Fill both blanks to complete the pytest project structure with a test file and a test function.

PyTest

tests/[1].py contains a function named [2] that pytest will run.

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

Atest_sample

Bsample_test

Ctest_example

Dexample_test

Attempts:

3 left

💡 Hint

Common Mistakes

Naming test functions without the 'test_' prefix.

Naming test files without the 'test_' prefix.

Test files should start with test_, so test_sample.py is correct. Test functions should also start with test_, so test_example is a valid function name.

5fill in blank

hard

Fill all three blanks to complete the pytest project structure with a test folder, test file, and test function.

PyTest

The folder '[1]' contains the file '[2].py' which has the function '[3]' that pytest runs.

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

Atests

Btest_utils

Ctest_process_data

Dutils

Attempts:

3 left

💡 Hint

Common Mistakes

Using folder names like 'utils' instead of 'tests'.

Naming test files or functions without the 'test_' prefix.

The standard pytest folder is tests. The test file should start with test_, so test_utils.py is correct. The test function also starts with test_, so test_process_data is valid.

Practice

1. Why should you place your test files inside a tests/ folder in a pytest project?

easy

A. To avoid writing test functions starting with test_

B. To make the tests run faster automatically

C. Because pytest only runs tests in the root folder

D. To keep test code separate and organized from application code

Solution

1. Step 1: Understand project organization

   Keeping tests in a separate tests/ folder helps keep the project clean and organized.

2. Step 2: Recognize pytest behavior

   pytest can find tests anywhere but organizing them in tests/ is a best practice for clarity and maintenance.

3. Final Answer:

   To keep test code separate and organized from application code -> Option D

4. Quick Check:

   Organized tests = tests/ folder [OK]

Hint: Put tests in a separate folder named tests for clarity [OK]

Common Mistakes:

• Thinking pytest only runs tests in root folder
• Believing tests run faster in tests/ folder
• Ignoring naming conventions for test functions

2. Which of the following is the correct way to name a test file so pytest can discover it automatically?

easy

A. test_example.py

B. mytests.py

C. example.py

D. TestExample.py

Solution

1. Step 1: Recall pytest naming rules

   pytest discovers test files that start with test_ or end with _test.py.

2. Step 2: Check each option

   test_example.py starts with test_, so pytest will find it automatically.

3. Final Answer:

   test_example.py -> Option A

4. Quick Check:

   File starts with test_ = discovered [OK]

Hint: Name test files starting with test_ for pytest discovery [OK]

Common Mistakes:

• Naming files without test_ prefix
• Using uppercase letters at start
• Assuming pytest finds any .py file

3. Given this project structure:

project/
  app.py
  tests/
    test_math.py
    utils/
      test_utils.py

Which files will pytest run by default when you run pytest in the project root?

medium

A. Only tests/utils/test_utils.py

B. Only tests/test_math.py

C. Both tests/test_math.py and tests/utils/test_utils.py

D. No tests run because of subfolder

Solution

1. Step 1: Understand pytest recursive discovery

   pytest looks inside the tests/ folder and all its subfolders for files starting with test_.

2. Step 2: Identify test files

   Both test_math.py and test_utils.py match naming rules and are inside tests/ or its subfolder.

3. Final Answer:

   Both tests/test_math.py and tests/utils/test_utils.py -> Option C

4. Quick Check:

   pytest finds tests recursively in tests/ [OK]

Hint: pytest finds test files recursively inside tests/ folder [OK]

Common Mistakes:

• Thinking pytest ignores subfolders
• Assuming only root tests/ files run
• Believing subfolders need special config

4. You have this test file named test_sample.py inside tests/ folder:

def sample_test():
    assert 1 + 1 == 2

When you run pytest, no tests are found. Why?

medium

A. Function name does not start with test_

B. File name should not start with test_

C. pytest requires tests to be inside root folder only

D. Missing import statement in test file

Solution

1. Step 1: Check function naming convention

   pytest discovers test functions only if their names start with test_.

2. Step 2: Analyze given function name

   The function is named sample_test, which does not start with test_, so pytest ignores it.

3. Final Answer:

   Function name does not start with test_ -> Option A

4. Quick Check:

   Test functions must start with test_ [OK]

Hint: Name test functions starting with test_ to be discovered [OK]

Common Mistakes:

• Assuming file name alone is enough
• Thinking pytest needs imports in test files
• Believing tests run only in root folder

5. In a large pytest project, how can you organize tests to keep them manageable and easy to run selectively?

hard

A. Put all tests in one big file named test_all.py

B. Use subfolders inside tests/ and add pytest.ini to configure test discovery

C. Name test functions randomly and rely on pytest to find them

D. Avoid using any configuration files to keep it simple

Solution

1. Step 1: Understand project scaling needs

   Large projects benefit from organizing tests in subfolders to separate features or modules.

2. Step 2: Use configuration files

   Adding a pytest.ini file helps customize test discovery and running specific groups of tests easily.

3. Final Answer:

   Use subfolders inside tests/ and add pytest.ini to configure test discovery -> Option B

4. Quick Check:

   Subfolders + pytest.ini = manageable large projects [OK]

Hint: Organize tests in subfolders and use pytest.ini config [OK]

Common Mistakes:

• Putting all tests in one file causing confusion
• Ignoring naming conventions for test functions
• Avoiding config files limits flexibility