QA Challenge# 9: Overcoming the Myth; Anyone Can Test

 Email Article  

Tweet  

  

Software QA and testing used to be fairly arbitrary (developers would test in their own way). But the trend has changed over the years as most software development shops have created a separate QA unit. Still, I’m often surprised to see how many organizations struggle to fill these positions – often not understanding what skills a QA person needs.

In some cases, I have seen people hiring fresh college graduates to fill position which requires skills. The perception is that anyone can pick up testing. Now, in some cases, this is valid. Don’t we all play with gadgets from ages 5 years to 95? So we get involved in doing small tests. But is it that easy when it comes to ensuring quality? I would say no, it is not. Quality assurance requires a much bigger skill set than just hitting keys on the keyboard or playing with mobile devices to test software or a product.

Software testing and quality assurance is not just “anyone’s job.” Each role requires a different skill set.  (Please see my blog on the differences between QA & QC).

Software Testing

Many people generalize testing skills into soft skills such as “attention to detail,” “analytical,” “communication.” Though these are all requirements for a good tester, I think there is another side of the coin which many people ignore – skills such as test planning, execution based on test plan, prioritization, creating a strategy for different testing projects, leading user acceptance, learning new technologies, etc.  I have found the 21 keys areas listed in the Test Process Improvement (TPI) model to be a very good basis to assess individual and organization capability for testing. I will write about how I implement this in a later blog.

With that being said, the role of the tester is changing and the expectations are increasing. The world quality report highlights new necessary skills for software testers such as being business focused (to bring real world scenarios into their testing effort) and improved technical skills (such as automation to improve efficiency). Organizations also desire better collaboration and would like to see testing, development and business working together on key projects focused on quality. I see this trend picking up and working very well for my clients.

Quality Assurance

Now let’s move from talking about testing to quality assurance. QA focuses on the critical processes necessary to build a product or services. The QA professional should understand the big picture and work toward process improvement initiatives aligned with strategic goals. Some key responsibilities include: the ability to assess a process, identify gaps in the process, create a change implementation plan, a quality plan and then ensure that new processes are followed through. I found the CSQA CBOK a good read for software professionals to learn more about quality assurance.