Dennis Doomen • 4/24/2023

What’s the “unit” in unit testing and why is it not a class

Read Original

The article discusses the fundamental question of what constitutes a 'unit' in unit testing, challenging the common assumption that it's a single class. It provides heuristics for defining test scope, emphasizes the cost and value of good tests, and uses a real-life database management example to illustrate how to decide what to test based on design intent and requirements, not just rigid rules.

0 comments
#unit testing #test-driven development #software quality
What’s the “unit” in unit testing and why is it not a class

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
React vs Browser APIs (Mental Model)
Jivbcoop • 3 votes
2
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 2 votes
3
Building Type-Safe Compound Components
TkDodo Dominik Dorfmeister • 2 votes
4
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes
5
Better react-hook-form Smart Form Components
Maarten Hus • 1 votes
6
Introducing RSC Explorer
Dan Abramov • 1 votes
7
The Pulse: Cloudflare’s latest outage proves dangers of global configuration changes (again)
The Pragmatic Engineer Gergely Orosz • 1 votes