What if 100% code coverage is a vanity metric? Learn to write fewer, better tests that focus on real-world behavior and reduce actual risk.
#1about 3 minutes
Why high test coverage creates a false sense of security
High test coverage and green builds often mask underlying issues, serving as vanity metrics that don't guarantee software reliability for users.
#2about 4 minutes
Identifying common but ineffective testing habits
Teams often test from habit rather than intent, leading to tests that mock behavior, only cover the happy path, and test what's easy instead of what's risky.
#3about 2 minutes
Closing the gap between unicorn testing and real-world failures
Testing often occurs in a "unicorn land" of perfect inputs and APIs, failing to account for real-world conditions like flaky dependencies, malformed data, and concurrency issues.
#4about 3 minutes
Shifting left to focus on behavior-driven development
Good testing should be part of requirements engineering, using practices like BDD and example mapping to define expected behavior before writing code.
#5about 3 minutes
Rethinking the traditional testing pyramid
The classic testing pyramid overemphasizes unit tests, which can create a false sense of security while ignoring critical bugs that live in integration points and business flows.
#6about 2 minutes
Adopting practical test design and risk-based prioritization
Mature test design involves techniques like boundary value analysis and decision tables, focusing on covering behavior and having the confidence to not test what doesn't matter.
#7about 5 minutes
Using BDD and example mapping to align teams
Behavior-Driven Development is a communication tool that uses concrete examples to create a shared understanding of requirements across developers, QA, and product teams.
#8about 2 minutes
How blame culture undermines your testing strategy
If testing is used to avoid blame rather than improve software, even the best tools will only automate the wrong behaviors and fail to address underlying cultural issues.
#9about 2 minutes
Actionable steps to immediately improve your testing
Start improving your testing strategy by deleting a useless test, asking risk-focused questions, modeling scenarios before coding, and spotting "cover your ass" patterns.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
04:03 MIN
Testing is a social and human-centric science
Excellent Software Testing
01:56 MIN
Adopting a reasonable and pragmatic testing approach
How not to test
02:50 MIN
Why traditional testing methods fail to guarantee quality
How will artificial intelligence change the future of software testing?
12:29 MIN
Q&A on testing strategies and team adoption
Write tests you love, not hate
03:00 MIN
Summary of key principles for better testing
Write tests you love, not hate
05:52 MIN
Architectural trade-offs and testing strategies
Interface Contracts in Microfrontend Architectures
03:12 MIN
Focusing on return on investment for tests
Why I Love End-2-End Tests and How To Get Them Right
04:45 MIN
Why traditional testing methods fail for microservice architectures
Lessons from Our API Past: Evolving to a Resilient API Future
Integration And E2E Testing: Are They Complementary or Interchangeable?The coronavirus pandemic’s effect on the software development industry was not as devastating as for, say, arts and tourism. In fact, the industry demonstrated significant resilience. According to Statista, only about a third of IT specialists worldw...
Kate Passby
How to create a test plan for software testingWhen creating new software, it's important to put it through rigorous testing. This improves IT security and helps to identify any problems. As software developers, the aim is to make the process of testing as painless as possible. This ensures the s...
Chris Heilmann
WWC24 Talk - Brenda Romero - Stay: Surviving and Thriving in TechBrenda Romero discusses her tech career journey, overcoming burnout, and inspiring future game developers at WWC24.Here is what she had to say in the video:Hey everyone! Thanks for joining us!Reflections on a Rough YearLast year, I gave a talk about ...
Daniel Cranney
The real reason we document our codeThe world of software development moves fast. Technology is constantly changing, as are the tools we use with it, and even the role of a programmer is itself constantly in flux. However, some aspects of software engineering are so foundational that w...
From learning to earning
Jobs that call for the skills explored in this talk.