Esc
↑↓ navigate   Enter open   Esc close

Testing & QA

Monkeypatch

/ˈmʌŋkiˌpætʃ/

Definition

Dynamically replacing a method or attribute at runtime — common in testing to override system or library behaviour.

Example in context

"In the test, monkeypatch requests.get to return a fake response — no actual HTTP calls during unit testing."

Related terms

  • Mock — A fake object replacing a real dependency in tests, with configurable return values and call verification.
  • Stub — A simplified replacement for a real object that returns predefined responses — simpler than a mock, no verification.
  • Unit test — A test that verifies a single function or module in isolation, without involving external systems.

Practice this term

Master Monkeypatch in context by working through exercises in the Testing & QA module. You'll see the term used in real engineering scenarios with multiple-choice, fill-in-the-blank, and matching drills.

Practice in exercises → Browse all words

Frequently Asked Questions

What does "Monkeypatch" mean?

Dynamically replacing a method or attribute at runtime — common in testing to override system or library behaviour.

How do you pronounce "Monkeypatch"?

"Monkeypatch" is pronounced /ˈmʌŋkiˌpætʃ/.

Can you use "Monkeypatch" in a sentence?

"In the test, monkeypatch requests.get to return a fake response — no actual HTTP calls during unit testing."