Temporary directory management in PyTest - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of using a temporary directory in pytest tests?

A temporary directory provides a safe, isolated space to create files or folders during tests without affecting the real file system. It is automatically cleaned up after the test finishes.

beginner

How do you access a temporary directory in a pytest test function?

You use the built-in pytest fixture called tmp_path or tmpdir. Just add it as a parameter to your test function, and pytest provides a fresh temporary directory path.

intermediate

What is the difference between tmp_path and tmpdir fixtures in pytest?

tmp_path returns a pathlib.Path object, which is modern and recommended. tmpdir returns a py.path.local object, which is older. Both create temporary directories.

beginner

Why is it important that pytest cleans up the temporary directory after the test?

Cleaning up prevents leftover files from filling disk space or interfering with other tests. It keeps tests independent and the environment clean.

beginner

Show a simple pytest test function that writes a file in a temporary directory using tmp_path.

import pytest

def test_write_file(tmp_path):
    file = tmp_path / "test.txt"
    file.write_text("hello")
    assert file.read_text() == "hello"

Which pytest fixture provides a temporary directory as a pathlib.Path object?

A tmp_path

B tmpdir

C tempfile

D temp_dir

tmp_path returns a pathlib.Path object for temporary directories. tmpdir returns a py.path.local object.

What happens to the temporary directory created by pytest after the test finishes?

A It remains on disk until manually deleted

B It is deleted automatically

C It is moved to a backup folder

D It is archived as a zip file

pytest automatically cleans up temporary directories after tests to keep the environment clean.

Why should tests use temporary directories instead of real folders?

A To permanently save test data

B To speed up test execution

C To share files between tests

D To avoid affecting real files and keep tests isolated

Temporary directories isolate test data and prevent side effects on real files.

Which of these is NOT a pytest fixture for temporary directories?

A tmp_path

B tempfile

C tmp_file

D tmpdir

tmp_file is not a pytest fixture. tmp_path and tmpdir are valid fixtures.

In pytest, how do you write text to a file inside a temporary directory using tmp_path?

A file = tmp_path / 'file.txt'; file.write_text('data')

B file = tmp_path.join('file.txt'); file.write('data')

C file = tmp_path.create_file('file.txt'); file.write('data')

D file = tmp_path.open('file.txt'); file.write('data')

tmp_path uses pathlib.Path syntax: use / to join paths and write_text() to write text.

Explain how pytest's temporary directory fixtures help keep tests independent and clean.

Think about why tests should not share or keep files after running.

Describe the difference between pytest's tmp_path and tmpdir fixtures and when to prefer one over the other.

Consider the Python standard library's pathlib module.

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