World Congress 2021 Jun 29, 2021

How not to test

Golo Roden

Chasing 100% test coverage won't save a poorly architected codebase. Discover why over-mocking hides bugs and how prototyping before TDD actually accelerates development.

Pause
Mute Enter Fullscreen
#1 about 6 min

Discovering automated testing through early programming experiences

How initial exposure to programming often lacks any concept of automated testing.

#2 about 7 min

Recognizing poorly structured code masquerading as hard to test

Code that feels impossible to test generally indicates poor architecture rather than intrinsic testing difficulty.

#3 about 6 min

Avoiding the trap of testing private code for coverage

Accessing internal state via reflection or inheritance to artificially boost code coverage represents an anti-pattern.

#4 about 4 min

Understanding why total code coverage is a false metric

Chasing full coverage often forces meaningless assertions and unnecessarily blocks automated deployment pipelines.

#5 about 8 min

Evaluating the dangers of over-mocking in integration tests

Relying heavily on fakes and stubs can create a false sense of security that breaks in reality.

#6 about 3 min

Managing test infrastructure and ensuring strict state reset

Automating infrastructure setups for tests guarantees independent execution free from stale states.

#7 about 4 min

Handling inherent asynchronicity when testing UI view components

Effective UI component testing requires strategies to handle asynchronous transitions and logic execution.

#8 about 4 min

Navigating the complexity of cross-browser view regression tests

Managing the fragility and slow execution times of large-scale browser automation suites requires realistic scoping.

#9 about 3 min

Knowing when to bypass test-driven development during prototyping

Strict test-first approaches hinder proof-of-concept exploration and add overhead before clear designs exist.

#10 about 2 min

Adopting a pragmatic approach to reasonable software engineering tests

Prioritizing realistic testing efforts yields better software quality than chasing arbitrary perfectionism or edge cases.

Matching moments

3:54 min

Weighing the benefits and tradeoffs of test-driven development

Alex Banul · LIVE

4:00 min

Adopting test-driven design as a strategic development methodology

Mirjam Aulbach · WWC 2022

6:24 min

Applying key software design rules to test code

Gil Zilberfeld · LIVE

3:09 min

Evaluating mocking strategies and user-centric integration testing

Rita Castro · WWC 2022

4:05 min

Using test automation as a catalyst for team collaboration

Augustin Gottlieb Augustin Gottlieb · WWC 2025

2:00 min

The software testing timeline and regression checking pitfalls

Ingo Philipp · LIVE

Upcoming sessions on this topic

Open session

World Congress 2026 North America

Reinventing Testing Practices in the AI Era

Eric Deandrea

Java Champion & Senior Principal Software Engineer, IBM

Eric Deandrea
Open session

World Congress 2026 North America

Agents Can't Iterate Against Tests That Lie

Rocky Warren

Senior Staff Software Engineer at Clipboard

Rocky Warren
Open session

World Congress 2026 North America

Testing React Backends Like a Pro: Mocking Databases with SQLite

David Morris

Solution Architect

David Morris
Open session

World Congress 2026 North America

One Repo, One Strategy: Scalable Full-Stack Testing in a Monorepo World

Bartosz Leczycki, Paweł Matynia

Bartosz Leczycki
Paweł Matynia
Open session

World Congress 2026 North America

How to generate business value through performance optimizations

Nikolai Sidiropulo

Software Engineer at Meta

Nikolai Sidiropulo
Open session

World Congress 2026 North America

There's no dark factory without better software verifiers

Dexter Horthy

Co-Founder, HumanLayer

Dexter Horthy