OnPath Testing

Saturday morning thought: Why do we call them "bugs" anyway?

Grace Hopper found that famous moth in a Harvard Mark II computer back in 1947, but programmers were calling problems "bugs" even before that.

Maybe because bugs are everywhere, hard to predict, and show up when you least expect them?

Or because fixing one sometimes reveals three more hiding nearby?

Either way, I'm grateful for the metaphor. "Debug" sounds so much better than "de-unexpected-software-behavior."

What's the weirdest bug you've encountered lately?

Product Manager: "How long will testing take?"

Me: "How long is a piece of string?"

PM: "But I need an estimate."

Me: "Give me the requirements."

PM: "We're still figuring those out."

Me: "Then I'm still figuring out the timeline."

This conversation happens approximately 847 times per week across the software industry. The solution isn't better estimation. It's better requirements.

You can't test what you can't define. You can't estimate what you can't scope.

Maybe we should all get t-shirts made.

Is your QA process slowing you down?

Common testing mistakes—like too many UI tests, skipped API checks, or blind trust in AI—can hide defects and slow your releases.

Our latest blog shows how the Test Pyramid helps SaaS teams catch issues early, speed up feedback, and deliver reliable software.

Read the full guide to learn more: https://www.onpathtesting.com/blog/the-test-pyramid-in-2026-still-relevant-still-necessary/