By Andréia Ribeiro
When I first heard the term “software tester,” I pictured someone who clicks buttons all day, hunting for bugs. My goal was simple: find what’s broken, report it, and move on. I thought success was measured by the number of defects logged. But as I dove deeper, I realised that testing is a vast, thoughtful discipline, and my initial view was just the tip of the iceberg.
The first, and perhaps most crucial, lesson was about mindset. Testing isn’t just a phase or a task; it’s a way of thinking. It’s a continuous process of critical inquiry, of curiosity, and of looking at software not just for what it does, but for what it could do, shouldn’t do, and might fail to do. This shift from “bug hunter” to “quality investigator” changed everything for me.
Knowing Your Role as a Tester
This new mindset directly impacts how I see my role. I learned that it’s easier to know if you're on the right track when you understand your purpose. If my only goal is to find bugs, I might become adversarial, or worse, I might miss the bigger picture. My role is broader and more valuable.
I now see that testing is not just about finding bugs. It’s about providing information. It’s about helping my team understand the quality and risks of the product we’re building. Am I checking if it meets the requirements? Am I exploring how it behaves under unexpected conditions? Am I thinking about the user’s experience and potential frustrations? When I ask these questions, I can adjust my path, focusing more on exploration here, more on confirmation there. My role is to learn, evaluate, and inform.
Rich and Diverse Views: My Compass
What helped me most was discovering that even experts have different, complementary perspectives. Having these clear views became my compass.
Glenford Myers gave me the classic, foundational view: “Software testing is the process of executing a program with the intent of finding errors.” This reminds me of the core investigative mission. There’s an active, purposeful search for problems.
Michael Bolton expanded my world dramatically. He says a tester is, among other things, “evaluating a product by learning about it through exploration, experimentation, observation, and inference.” This resonates deeply. It’s not just execution; it’s exploration. It’s about designing little experiments, observing outcomes, and drawing conclusions. It’s creative and intellectual.
Elisabeth Hendrickson phrased it in a beautifully simple way: “Testing is interacting with software or a system, observing its behaviour, and comparing your expectations.” This is my daily mantra. Interact. Observe. Compare. It frames every test, from the simplest check to the most complex exploratory session.
Edsger W. Dijkstra offered the vital dose of humility: “Software testing can be a very effective way to show the presence of bugs, but it is hopelessly inadequate for showing their absence.” No amount of testing can prove software is perfect. My job isn’t to “guarantee” anything, it’s to uncover enough information so the team can make an informed decision about release.
Combining the Views: My Emerging Practice
At first, these views seemed to contradict each other. Now I see they are threads in the same fabric.
I start with Myers’ intent: I execute with the purpose of finding issues. I use Hendrickson’s model: I interact, observe, and compare. To do that effectively, I adopt Bolton’s approach: I explore, experiment, and learn about the product’s true behaviour. And throughout, I temper my conclusions with Dijkstra’s wisdom: I know that passing my tests doesn’t mean “bug-free,” it means “these specific conditions, at this time, produced the expected results.”
For a beginner, this blend is incredibly powerful. It frees me from the pressure of finding “all” the bugs. Instead, I focus on conducting thoughtful, varied, and well-informed investigations. I am not just a button-clicker; I am a learner, an experimenter, an observer, and a communicator.
The journey from seeing testing as a simple bug hunt to understanding it as a rich, information-gathering discipline has been transformative. It turns out that having multiple, clear visions doesn’t create confusion, it creates depth. And for a beginner like me, that depth is what makes this field so fascinating. Every day is a chance to learn, to experiment, and to contribute to building something better.
Comments
Post a Comment