monkeypatch.chdir in PyTest - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output after using monkeypatch.chdir?

Consider the following pytest test function that uses monkeypatch.chdir to change the current working directory.

What will be the printed output when this test runs?

PyTest

import os
import pytest

def test_change_dir(monkeypatch):
    original_dir = os.getcwd()
    monkeypatch.chdir("/tmp")
    current_dir = os.getcwd()
    print(current_dir)
    print(original_dir == current_dir)

A

Original directory path
True

B

/tmp
True

C

Original directory path
False

D

/tmp
False

💡 Hint

Think about what monkeypatch.chdir does to the current working directory during the test.

The monkeypatch.chdir("/tmp") changes the current working directory to /tmp inside the test. So os.getcwd() returns /tmp. The original directory is different, so the comparison is False.

❓ assertion

intermediate

Which assertion correctly verifies directory change with monkeypatch.chdir?

You want to write a pytest test that confirms the current working directory changes to /var using monkeypatch.chdir. Which assertion is correct?

PyTest

import os
def test_dir_change(monkeypatch):
    monkeypatch.chdir("/var")
    # Which assertion below is correct?

A assert os.getcwd() == "/tmp"

B assert os.getcwd() != "/var"

C assert os.getcwd() == "/var"

D assert os.getcwd() is "/var"

💡 Hint

Use == to compare strings, not is.

The correct way to check the current directory is to compare the string returned by os.getcwd() with the expected path using ==. Using is compares object identity, which is not reliable for strings.

🔧 Debug

advanced

Why does this test fail when using monkeypatch.chdir?

Examine the test below. It is supposed to change the directory to /home/user and check it. However, it fails. What is the reason?

PyTest

import os
def test_fail_dir_change(monkeypatch):
    monkeypatch.chdir("/home/user")
    assert os.getcwd() == "/home/user"

# The test fails with AssertionError.

A The directory /home/user does not exist in the test environment.

B monkeypatch.chdir does not actually change the directory.

C The assertion syntax is incorrect.

D os.getcwd() returns a relative path, not absolute.

💡 Hint

Check if the directory exists in the environment where the test runs.

If the directory /home/user does not exist, monkeypatch.chdir cannot change to it, so os.getcwd() remains unchanged, causing the assertion to fail.

❓ framework

advanced

How does monkeypatch.chdir affect tests in pytest?

Which statement best describes the behavior of monkeypatch.chdir in pytest tests?

A It permanently changes the working directory for all tests in the session.

B It changes the current working directory only for the duration of the test function and restores it afterward.

C It changes the directory globally and does not restore it after the test.

D It only simulates directory change without affecting os.getcwd().

💡 Hint

Think about test isolation and cleanup.

monkeypatch.chdir temporarily changes the current working directory during the test and automatically restores it after the test finishes, ensuring tests do not affect each other.

🧠 Conceptual

expert

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

Why is it better to use monkeypatch.chdir instead of manually changing directories with os.chdir in pytest tests?

A monkeypatch.chdir automatically restores the original directory after the test, preventing side effects.

B monkeypatch.chdir changes directories faster than os.chdir.

C monkeypatch.chdir changes the directory globally for all running processes.

D monkeypatch.chdir works outside of pytest tests as well.

💡 Hint

Consider test isolation and cleanup.

Using monkeypatch.chdir ensures the test environment is cleaned up by restoring the original directory after the test, avoiding interference with other tests. Manual os.chdir calls can cause side effects if not properly restored.