Hynek Schlawack • 6/21/2022

“Don’t Mock What You Don’t Own” in 5 Minutes

Read Original

This article delves into the software testing principle 'Don't Mock What You Don't Own,' which advises against using mock objects for third-party dependencies. It explains the reasoning behind the rule, demonstrates the downsides of mocking external APIs with a Python/Docker registry example, and suggests using stubs or verified fakes as better alternatives for writing robust tests.

0 comments
#testing #unit testing #test doubles
“Don’t Mock What You Don’t Own” in 5 Minutes

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
The Beautiful Web
Jens Oliver Meiert • 2 votes
2
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane • 1 votes
3
LLM Use in the Python Source Code
Miguel Grinberg • 1 votes
4
Wagon’s algorithm in Python
John D. Cook • 1 votes
5
An example conversation with Claude Code
Dumm Zeuch • 1 votes