# from David Cantrell
# on Wednesday 03 September 2008 09:57:
>If, like one of my previous employers, you make widgets, you test
>completed widgets, you analyse how they fail, the analyst suggests
>how to improve the manufacturing process to prevent a common failure,
>and TPTB then ignore his report - then "Quality Assurance: you're
>doing it wrong".
So, say I make a super lightweight track bike with skinny tires charged
to 120psi and a big fixed gear. Then 40 of my 50 testers take it out
on the trails and try to jump logs with it, but only one guy takes it
to the track and the other 9 try to use it to open cans of beets.
They all consider it to have failed, and all of them put their reports
in a big pile of red paper on my desk. When I get to the tenth report
about "bogs down in sand" or "hard to maneuver on logs", I'm probably
not going to have the stamina to read through the entire pile to find
the one important report from the tester who took it to the track and
found that the bottom bracket seized at full speed.
If I see two reports about canned beets, I'm likely to just give up.
So, we all agree that testing is good, but please... test the *code*?
"The old version of the installer is broken"? So what?
--Eric
--
The first rule about Debian is you don't talk about Debian
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
