Is your QA Team effective? -

Is your QA team effective? I have come to know that many QA people I have had to face have more validators and software Breaking expert

What I mean by the verifier, they take action through all the scenarios, basically go through the application and make sure that what is considered

They verify what I mean with breakers, but they work hard to find such scenarios that break software and expose the defects.

Is your findings similar?

Historical notes about breaking the software were a team inside IBM, which was called the Black Team in 80's. He had a culture to say that when he had "successful" to encourage the identification of software to promote the identity of the flaws. They consider their work "failure" when they failed to find / detect any errors in the software. On the other hand, the result of their "failure" was a very reliable software ... and book: "What to break software: A practical guide to testing" by James Whittaker

< P>

In many instances I would be happy if QA did this. My experience is that if QA is present in all, then often it involves recruiting bad payment agency with a bad sense of business. QA is well-difficult, such as programming difficult, it is rarely managed or managed as a critical part of the development process.

On the other hand, the best QA I worked with 20+ PC ghost images, and knew what to do with them, they were DB ninja, who could communicate with end users too. Machines were tested on a large scale with the hardware, the lead was strong, knew when it was pushed and let it go, it knew the customers, and knew how the developers thought we soon knew it That our good standard standards were not identical to customers. Unfortunately this product was still a loose pile of junk, this is business, but it rarely crashed and customers liked it.