Temporary directory management in PyTest - Test Execution Trace

Test Overview

This test uses pytest's tmp_path fixture to create a temporary directory. It verifies that a file can be created and read inside this temporary directory.

Test Code - pytest

PyTest

import pytest

def test_create_and_read_file(tmp_path):
    # Create a file path inside the temporary directory
    file_path = tmp_path / "testfile.txt"
    # Write text to the file
    file_path.write_text("Hello, pytest!")
    # Read the text back
    content = file_path.read_text()
    # Assert the content is as expected
    assert content == "Hello, pytest!"

Execution Trace - 7 Steps

Step	Action	System State	Assertion	Result
1	Test starts	pytest test runner initialized	—	PASS
2	pytest provides tmp_path fixture as a temporary directory	A new empty temporary directory is created for the test	—	PASS
3	Create a file path 'testfile.txt' inside tmp_path	Temporary directory is empty, file path is prepared	—	PASS
4	Write text 'Hello, pytest!' to the file	File 'testfile.txt' now exists with content 'Hello, pytest!'	—	PASS
5	Read text content from the file	File content read as 'Hello, pytest!'	—	PASS
6	Assert that the read content equals 'Hello, pytest!'	Content matches expected string	assert content == 'Hello, pytest!'	PASS
7	Test ends and temporary directory is cleaned up	Temporary directory and files removed	—	PASS

Failure Scenario

Failing Condition: The file content read does not match the expected string

Execution Trace Quiz - 3 Questions

What does the tmp_path fixture provide in this test?

A A temporary file only

B A temporary directory unique to the test

C A permanent directory shared across tests

D A network location for storing files

Key Result

Using pytest's tmp_path fixture ensures tests have a clean, isolated temporary directory that is automatically removed after the test, preventing side effects and making tests reliable.

Practice

1. What is the main purpose of using the tmp_path fixture in pytest?

easy

A. To create a temporary directory for test files that is cleaned up automatically

B. To permanently store test results on disk

C. To speed up test execution by caching files

D. To replace the need for writing assertions in tests

Solution

1. Step 1: Understand the role of tmp_path in pytest

   The tmp_path fixture provides a temporary directory unique to each test run.

2. Step 2: Recognize the cleanup behavior

   Files created in this directory are removed after the test finishes, keeping tests clean and isolated.

3. Final Answer:

   To create a temporary directory for test files that is cleaned up automatically -> Option A

4. Quick Check:

   Temporary directory = safe test files [OK]

Hint: Remember tmp_path auto-cleans test files after each test [OK]

Common Mistakes:

• Thinking tmp_path stores files permanently
• Confusing tmp_path with caching mechanisms
• Believing tmp_path replaces assertions

2. Which of the following is the correct way to use the tmp_path fixture in a pytest test function?

easy

A. def test_example():\n file = tmp_path / 'test.txt'\n file.write_text('hello')

B. def test_example(tmp_path):\n file = tmp_path / 'test.txt'\n file.write_text('hello')

C. def test_example(tmp_path):\n file = open('test.txt', 'w')\n file.write('hello')

D. def test_example():\n tmp_path = '/tmp/test'\n file = tmp_path + '/test.txt'\n write(file, 'hello')

Solution

1. Step 1: Identify correct fixture usage

   pytest injects tmp_path as a function argument automatically.

2. Step 2: Check file creation syntax

   Using tmp_path / 'filename' creates a Path object; write_text() writes content correctly.

3. Final Answer:

   def test_example(tmp_path):\n file = tmp_path / 'test.txt'\n file.write_text('hello') -> Option B

4. Quick Check:

   Fixture as argument + Path write = correct [OK]

Hint: Always accept tmp_path as a test function argument [OK]

Common Mistakes:

• Assigning tmp_path manually instead of using fixture
• Using open() without tmp_path directory
• Not passing tmp_path as a parameter

3. What will be the output of the following pytest test code snippet?

def test_write_read(tmp_path):
    file = tmp_path / 'data.txt'
    file.write_text('pytest')
    content = file.read_text()
    assert content == 'pytest'

medium

A. Runtime error because file is not created

B. Test fails due to assertion error

C. Syntax error in test code

D. Test passes successfully

Solution

1. Step 1: Analyze file writing and reading

   The code writes 'pytest' to a file in tmp_path, then reads it back correctly.

2. Step 2: Check assertion correctness

   The read content matches the written string 'pytest', so assertion passes.

3. Final Answer:

   Test passes successfully -> Option D

4. Quick Check:

   Write then read same text = pass [OK]

Hint: Write and read text in tmp_path matches, so assert passes [OK]

Common Mistakes:

• Assuming file is not created automatically
• Confusing assertion logic
• Thinking tmp_path is a string path, not Path object

4. Identify the error in this pytest test using tmp_path:

def test_error(tmp_path):
    file = tmp_path + '/file.txt'
    file.write_text('error')

medium

A. File write_text method does not exist

B. Missing assertion statement causes test failure

C. Using + operator to join paths causes a TypeError

D. tmp_path fixture is not passed as argument

Solution

1. Step 1: Check path joining method

   tmp_path is a Path object; using + with string causes TypeError.

2. Step 2: Correct path joining

   Use tmp_path / 'file.txt' to join paths properly.

3. Final Answer:

   Using + operator to join paths causes a TypeError -> Option C

4. Quick Check:

   Path + string = error; use / operator [OK]

Hint: Join paths with / operator, not + [OK]

Common Mistakes:

• Using + to join Path and string
• Forgetting to pass tmp_path as parameter
• Assuming write_text is invalid method

5. You want to create a nested directory structure inside tmp_path and write a file in the deepest folder. Which code snippet correctly does this in pytest?

hard

A. def test_nested(tmp_path):\n nested_dir = tmp_path / 'a' / 'b' / 'c'\n nested_dir.mkdir(parents=True)\n file = nested_dir / 'file.txt'\n file.write_text('nested')

B. def test_nested(tmp_path):\n nested_dir = tmp_path / 'a' / 'b' / 'c'\n nested_dir.mkdir()\n file = nested_dir / 'file.txt'\n file.write_text('nested')

C. def test_nested(tmp_path):\n nested_dir = tmp_path / 'a' / 'b' / 'c'\n file = nested_dir / 'file.txt'\n file.write_text('nested')

D. def test_nested(tmp_path):\n nested_dir = tmp_path + '/a/b/c'\n nested_dir.mkdir(parents=True)\n file = nested_dir / 'file.txt'\n file.write_text('nested')

Solution

1. Step 1: Understand nested directory creation

   To create nested folders, mkdir(parents=True) is needed to create all missing parents.

2. Step 2: Check path joining and file writing

   Using / operator joins paths correctly; writing text to file is valid.

3. Step 3: Identify errors in other options

   def test_nested(tmp_path):\n nested_dir = tmp_path / 'a' / 'b' / 'c'\n nested_dir.mkdir()\n file = nested_dir / 'file.txt'\n file.write_text('nested') misses parents=True, so mkdir fails if parents missing. def test_nested(tmp_path):\n nested_dir = tmp_path / 'a' / 'b' / 'c'\n file = nested_dir / 'file.txt'\n file.write_text('nested') does not create directories before writing file. def test_nested(tmp_path):\n nested_dir = tmp_path + '/a/b/c'\n nested_dir.mkdir(parents=True)\n file = nested_dir / 'file.txt'\n file.write_text('nested') uses + operator incorrectly for paths.

4. Final Answer:

   def test_nested(tmp_path):\n nested_dir = tmp_path / 'a' / 'b' / 'c'\n nested_dir.mkdir(parents=True)\n file = nested_dir / 'file.txt'\n file.write_text('nested') -> Option A

5. Quick Check:

   mkdir(parents=True) + / operator = correct [OK]

Hint: Use mkdir(parents=True) to create nested folders [OK]

Common Mistakes:

• Not using parents=True for nested mkdir
• Using + operator to join paths
• Writing file before creating directories