QA people are not testers, or are they?

Test Pappy

The world of software companies is full of testers and test departments named as Quality Assurance. There is a long ongoing quarrel if QA and Test is the same or not. Long story short, no they are not the same! But a person working in QA needs a lot of skills a good tester has.

My official job title is QA Lead, but I deliberately use the term Test Lead and have it proudly in my signature. Because that’s what I am doing, and that is even what my job description says. Calling software testers by the name of quality assurance implies for many that there is a step in the “production” process that assures the quality. And this is wrong!

Quality Assurance is a term coming from the world of manufacturing. People working in Quality Assurance are monitoring and auditing the production process and keep an eye on it, that…

View original post 501 more words

Do testers really prevent bugs?

Testing the Mind

The question of whether testers prevent bugs or find them is a fairly regular tester conversation.

When you find a bug in the software you have clearly found a bug. It makes no difference whether you were actively testing the software, trying to use the software, or simply clicking around randomly, by performing some actions and recognising that a problem occurred you were testing.

Many testers do much more than testing the actual software product and many want to somehow define what these additional things are. Actions like reviewing requirements, planning releases, training users can all fall to testers. So at what point does testing really start?

Richard Bradshaw argues that finding a bug in the requirements is still just finding a bug. You might have found it earlier but you hadn’t prevented it. A mistake in requirements can still be considered a bug. Your knowledge of the system, the…

View original post 958 more words

You Are Not Agile . . . If You Do Waterfall

Software Process and Measurement

The spiral method is just one example of a Agile hybrid. The spiral method is just one example of a Agile hybrid.

Many organizations have self-titled themselves as Agile. Who wouldn’t want to be Agile? If you are not Agile, aren’t you by definition clumsy, slow or dull? Very few organizations would sign up for those descriptions; however, Agile in the world of software development, enhancements and maintenance means more than being able to move quickly and easily. Agile means that a team or organization has embraced a set of principles that shape behaviors and lead to the adoption of a set of techniques. When there is a disconnect between the Agile walk and the Agile talk, management is often a barrier when it comes to principles and practitioners are when it comes to techniques. Techniques are often deeply entrenched and require substantial change efforts. Many organizations state they are using a hybrid approach to Agile to transition from a more…

View original post 644 more words