Orbit · Explore

Programming · by Sleepy Coder · 2026-10-16

What's your rule for when to write a test?

I used to aim for 100% coverage, now I test behavior at boundaries and bugs I've already seen. Less brittle, more sleep.

31 sparks · 16 comments

Comments

Sara Ahmed · 13 likes

Hot take: testing philosophy is one of those things that sounds simple until you try it with real constraints.

Kabir Khan · 12 likes

wait until you see the invoice

Angel Reyes · 0 likes

my wallet felt that

Luciana Vargas · 7 likes

Would love to see actual data on testing philosophy instead of vibes. Anyone have links

Miguel Santos · 4 likes

I've lived this exact meeting

Solar Otter · 5 likes

Getting started with testing approaches is easier than a year ago. That part is underrated.

Alma Nilsson · 12 likes

this. so much this

Lucas Silva · 4 likes

Is anyone else tired of the hype around testing philosophy, feels like every other post is about it

Midnight Noodle · 4 likes

As someone who does this for a living, the biggest cost with testing philosophy is the stuff nobody puts in the demo.

Amelia Hughes · 0 likes

send help

Jasmine Cruz · 0 likes

I've lived this exact meeting

Luca Bianchi · 1 likes

We tried a new testing approach last quarter. Small stuff went well, but it got messy at scale!

Silver Runner · 12 likes

Good point, didn't think of that

Faisal Al Saud · 6 likes

can you share what you changed

Camila Rocha · 0 likes

We ran the numbers on our testing approach. The payoff came later than expected!

Hugo Sánchez · 0 likes

I'm more of an enthusiast than a pro but testing philosophy has been fun to tinker with on weekends