J. B. Rainsberger, TDD coach and software consultant, joins Marco to challenge common assumptions about software testing. They discuss why JB argues that “integrated tests are a scam,” how testing choices affect design and refactoring, and what teams get wrong when they rely too heavily on end-to-end tests. The conversation draws on decades of real-world experience working with development teams of all sizes.

💡 Topics in this episode:

What “integrated tests” really are and why they cause problems
Micro tests, fast feedback, and confidence-driven testing
When deleting tests is the right decision
How tests create pressure on system design
Collaboration and contract tests explained
Why there is no single testing best practice
Practical advice for junior and senior developers

New episodes every other Wednesday. Subscribe for more developer-focused conversations.

⏰ Timestamps:

(00:00) Teaser

(01:24) Intro

(02:44) How J. B. got into testing

(06:12) What “integrated tests” actually mean

(10:42) Stop asking “what’s the right test size?”

(13:22) Removing irrelevant details from tests

(15:30) Refactoring, coupling, and deleting tests

(18:08) “There’s no best practice.”

(23:52) Old TDD books and timeless ideas

(26:01) Collaboration and contract tests explained

(33:53) “99.5% of your tests can be micro tests”

(46:21) Do you want to be right or solve the problem?

(01:00:48) Advice for junior developers

(01:19:32) Testing strategy distilled

(01:23:58) Manual QA testing

(01:29:44) Giveaway

(01:33:15) Rapid fire and outro

🎥 Watch the full episode on YouTube: https://youtu.be/j0NjFsb-at8

Are Integrated Tests a Scam? TDD, Architecture, Fast Feedback – J. B. Rainsberger