Claudiu Draghia

I have been a tester since 2004. I have taken many roles in 13 years but have always considered myself a tester. I have not seen it all, but I have seen a lot. I have been ecstatic when I found bugs that were on the verge of an insane check and terribly ashamed when I missed something that made using the product difficult or impossible in production. I have hidden away in my projects and company believing that I am a good tester I, and I have been on stage, in front of hundreds of people, expecting the one question that will make me realize how stupid my assumptions are.

The Testing Map aims at covering, in visual form, the most important information a software tester should know. There is one area which tackles processes in particular. I will talk about this area in the lines that follow.

Within the testing and software development world, there seems to be a confusion about what Quality Assurance, Quality Control, Checking and Testing refer to. I will show you the differences through my eyes and experience.

I’ve spent the past ten years of my life in the IT industry, living and breathing for quality software testing. I started out as a tester and even though I’ve spent my last few years as a Quality Manager, I’m still a tester at heart. In all my experience, I’ve always encountered one phenomenon that stands out from the rest. This is the tester’s plight, wherein managers will often believe that literally anyone can test applications, their confusion whenever bugs still happen in a productive environment, even after months of extensive testing in a sandbox and the overall state of a demanding but yet unrecognized profession.