The general concept of software QA is fairly straightforward: to ensure that the solution is truly ready for market. However, this is easier said than done. Devising a test management strategy that adequately vets a solution and filters out potential defects demands a concerted effort from testers as well as the developers they will be working with (assuming a DevOps mentality).
I once consulted for a company to give a week-long course on testing and QA. It was a survey course covering a wide range of topics. As I was setting up, I was chatting with students in the room. One man came over to me and said: “I have been testing for six months, and I am completely bored. I plan on getting a different job in software, either in the company or outside, but it won’t be in testing. I know testing is important—very important—but it’s so boring. It’s not for me. This is my last chance: I hope I can learn something from this class that makes testing more interesting or challenging.”
Just about every organization goes through times when the internal team cannot execute a testing project fast enough. Reasons range from the magnitude of the project, to lack of an effective test strategy, to staff positions going unfilled. The speed of Agile development and rapid delivery of product also increases testing technical debt.
Michael Hackett – Senior Vice President of LogiGear Corporation and Editor-in-Chief of Logigear Magazine, weighs in on how to improve existing testing processes.
On the whole, everyone wants to do a great job, have a better work environment, happy clients and customers, and to be employed by a company earning lots of money. All great goals!Continue reading