We just had our all-hands meeting and I'm watching the slides of our various development teams about their accomplishments for the year - from the release of our products to technology upgrades to some major refactors. I started imagining what our QA slide would look like, but then I kept getting stuck. At the end of it all, the most important gauge of software development in general is that we've delivered working software. But in what area can the QA team take credit for the success? Is success in the number of bugs found during testing? When I was starting my new job, I was happy that I was able to catch a lot of bugs before the changes were deployed to production. One day, a developer asked me this: "Why is QA happy that there are a lot of bugs?" I told him, "Well, it's my job to find bugs before someone else finds them." And then he dryly replied, "I see." It got me thinking later if my mindset is actually correct. With the introduction of...
Software testing and etc.