DEV Community

Discussion on: Stop lying to yourself when testing

Collapse
 
klamping profile image
Kevin Lamping

Some very good points! I think this would make a great follow up post, going through different scenarios and how to ensure you've covered the major scenarios, but not gone too far in testing unneeded scenarios.

Collapse
 
itsasine profile image
ItsASine (Kayla)

I think it stems from more tests being assumed to always mean better. And having lots of tests obviously means we'll never have bugs ever.

Bugs will always happen, but good tests mean they get caught earlier and hopefully before things get merged to the main codebase, so yay! But that doesn't mean there are no bugs. And that doesn't mean that there are no missing requirements. It just means tests passed :P

And there will always be someone writing a test to verify the sky isn't red, and someone looking at the metrics and being happy test count and coverage increased.