monkeypatch.chdir in PyTest - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does monkeypatch.chdir do in pytest?

monkeypatch.chdir temporarily changes the current working directory during a test. After the test, it restores the original directory automatically.

beginner

Why use monkeypatch.chdir instead of os.chdir directly in tests?

Using monkeypatch.chdir ensures the directory change is temporary and automatically reversed after the test. This avoids side effects on other tests.

beginner

How do you use monkeypatch.chdir in a pytest test function?

Pass monkeypatch as a test argument, then call monkeypatch.chdir("path/to/dir") inside the test to change directory temporarily.

intermediate

What happens if you call monkeypatch.chdir with a non-existent directory?

It raises a FileNotFoundError immediately, just like os.chdir. The test will fail unless handled.

intermediate

Can monkeypatch.chdir be used multiple times in the same test?

Yes, you can call it multiple times to change directories during a test. Each call changes the directory temporarily until the test ends.

What is the main benefit of using monkeypatch.chdir in pytest tests?

A It permanently changes the working directory.

B It creates a new directory.

C It deletes the current directory.

D It temporarily changes the working directory and restores it after the test.

monkeypatch.chdir temporarily changes the directory for the test and restores the original directory automatically.

What happens if monkeypatch.chdir is called with a path that does not exist?

A It raises a <code>FileNotFoundError</code>.

B It creates the directory automatically.

C It changes to the root directory.

D It silently ignores the error.

Calling monkeypatch.chdir with a non-existent path raises a FileNotFoundError, just like os.chdir.

How do you get access to monkeypatch in a pytest test function?

A Add it as a parameter to the test function.

B Import it from pytest manually.

C Call a global function.

D Use a decorator.

pytest injects monkeypatch as a parameter when you add it to the test function arguments.

Which of these is a correct use of monkeypatch.chdir?

A monkeypatch.chdir()

B monkeypatch.chdir('/tmp')

C monkeypatch.chdir(123)

D monkeypatch.chdir(None)

You must provide a valid directory path string to monkeypatch.chdir.

After a test using monkeypatch.chdir finishes, what is the current working directory?

A The home directory.

B The directory set by monkeypatch.

C The original directory before the test.

D The root directory.

pytest restores the original working directory after the test ends.

Explain how monkeypatch.chdir helps keep tests isolated and why that is important.

Think about what happens if tests change directories without restoring.

Describe the steps to use monkeypatch.chdir in a pytest test function.

Focus on how pytest provides monkeypatch and how you call the method.

Practice

1. What is the main purpose of using monkeypatch.chdir in pytest tests?

easy

A. To temporarily change the current working directory during a test

B. To permanently change the system's default directory

C. To mock HTTP requests in tests

D. To patch environment variables permanently

Solution

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

   Monkeypatch is used to temporarily modify or replace parts of the system during tests without permanent changes.

2. Step 2: Focus on the chdir method

   monkeypatch.chdir specifically changes the current working directory only for the duration of the test.

3. Final Answer:

   To temporarily change the current working directory during a test -> Option A

4. Quick Check:

   monkeypatch.chdir = temporary directory change [OK]

Hint: Remember monkeypatch changes things only during tests [OK]

Common Mistakes:

• Thinking it changes directories permanently
• Confusing with mocking HTTP requests
• Using it to patch environment variables permanently

2. Which of the following is the correct syntax to change the current directory to '/tmp' using monkeypatch in a pytest test function?

easy

A. monkeypatch.chdir('/tmp')

B. monkeypatch.chdir = '/tmp'

C. monkeypatch.change_dir('/tmp')

D. monkeypatch.chdir('/tmp', permanent=True)

Solution

1. Step 1: Recall the method name and usage

   The correct method to change directory temporarily is monkeypatch.chdir(path).

2. Step 2: Check each option for syntax correctness

   Assignment like chdir = '/tmp' is incorrect; it must be called as a function. change_dir is the wrong method name. Adding permanent=True is unsupported.

3. Final Answer:

   monkeypatch.chdir('/tmp') -> Option A

4. Quick Check:

   Correct method call = monkeypatch.chdir(path) [OK]

Hint: Use monkeypatch.chdir(path) exactly as a function call [OK]

Common Mistakes:

• Assigning instead of calling the method
• Using wrong method names like change_dir
• Adding unsupported arguments

3. Given the following pytest test code, what will be the output of print(os.getcwd()) inside the test?

import os

def test_change_dir(monkeypatch):
    original_dir = os.getcwd()
    monkeypatch.chdir('/tmp')
    print(os.getcwd())
    assert os.getcwd() != original_dir

medium

A. original_dir value

B. /tmp

C. Raises FileNotFoundError

D. Empty string

Solution

1. Step 1: Understand what monkeypatch.chdir does

   It temporarily changes the current working directory to the given path during the test.

2. Step 2: Analyze the print statement after monkeypatch.chdir

   Since monkeypatch.chdir('/tmp') is called, os.getcwd() will return '/tmp' inside the test.

3. Final Answer:

   /tmp -> Option B

4. Quick Check:

   os.getcwd() after monkeypatch.chdir('/tmp') = '/tmp' [OK]

Hint: After monkeypatch.chdir(path), os.getcwd() returns path [OK]

Common Mistakes:

• Expecting original directory instead of changed one
• Thinking it raises an error if directory exists
• Assuming it returns empty string

4. Identify the error in this pytest test using monkeypatch.chdir:

import os

def test_dir_change(monkeypatch):
    monkeypatch.chdir('/nonexistent')
    assert os.getcwd() == '/nonexistent'

medium

A. assert statement syntax is incorrect

B. monkeypatch.chdir should be called without arguments

C. The directory '/nonexistent' may not exist, causing an error

D. os.getcwd() cannot be used inside tests

Solution

1. Step 1: Check the directory path used in monkeypatch.chdir

   The path '/nonexistent' likely does not exist on the system, which causes an error when changing directory.

2. Step 2: Understand monkeypatch.chdir behavior with invalid paths

   It tries to change directory and will raise FileNotFoundError if the path is invalid.

3. Final Answer:

   The directory '/nonexistent' may not exist, causing an error -> Option C

4. Quick Check:

   Invalid path in monkeypatch.chdir causes error [OK]

Hint: Ensure directory exists before monkeypatch.chdir call [OK]

Common Mistakes:

• Thinking monkeypatch.chdir works without a valid path
• Believing os.getcwd() is invalid in tests
• Misreading assert syntax

5. You want to test a function that reads a file named 'data.txt' in the current directory. How can you use monkeypatch.chdir to test this function with a temporary test folder '/tmp/testfolder' containing 'data.txt' without affecting other tests?

hard

A. Copy 'data.txt' to the original directory and run the test there

B. Change directory globally before running all tests

C. Use monkeypatch.chdir('/tmp/testfolder') and set permanent=True

D. Use monkeypatch.chdir('/tmp/testfolder') inside the test to change directory temporarily

Solution

1. Step 1: Understand the need for isolation in tests

   Tests should not affect global state or other tests, so changing directory temporarily is best.

2. Step 2: Use monkeypatch.chdir to change directory only during the test

   Calling monkeypatch.chdir('/tmp/testfolder') changes the current directory only inside the test, isolating file access.

3. Final Answer:

   Use monkeypatch.chdir('/tmp/testfolder') inside the test to change directory temporarily -> Option D

4. Quick Check:

   Temporary directory change isolates test file access [OK]

Hint: Use monkeypatch.chdir(path) to isolate file-based tests [OK]

Common Mistakes:

• Changing directory globally affecting other tests
• Copying files unnecessarily
• Using unsupported permanent argument