
What to Test—and When
One of the biggest misconceptions in software development is that “testing” is a single phase, a checkbox, or a responsibility that starts after development ends.

One of the biggest misconceptions in software development is that “testing” is a single phase, a checkbox, or a responsibility that starts after development ends.

Maybe you even memorised them during your ISTQB exam or scribbled them on a post-it during your first QA bootcamp.
But in real-world projects, the “seven testing principles” often sound like fortune cookie wisdom.

No deep technical knowledge is required—this blog is designed for anyone involved in building, testing, managing, or supporting software products who wants to understand why catching bugs early isn’t just a nice-to-have, but a strategic advantage.

You’ve heard it. Maybe you’ve even said it. The developer pushes their code, closes the ticket, and confidently declares, “It works on my machine.”
And that, right there, is often where real software testing begins.