I've been out of "black box" software testing for a long time. It used to be a problem that bug reports from testers would be closed for reasons like “no one will ever do that."
That is, the argument was that, yes, this result would be bad, but no one (or an insignificant number of people) would ever see it.
Is that still a problem?
Comments
Displaying 0 of 1 comments
Brian Marick
In response to this postOld fogie anecdote time!
I was once told that there was a known spacecraft-destroying bug in the Space Shuttle software. It would happen if the pilot pushed the wrong button during ascent. They chose not to (attempt to) fix it. A known bug that could be avoided by telling a highly-trained pilot "see that button? don't push it until you're in orbit" was seen as less risky than changing the code.
(1/2)
I once helped test one of the early true multiprocessor Unix kernels (more than one processor could be running kernel code at the same time). My contribution was a program called `churn` that was easily tweaked to hammer on particular system calls with many processors at the same time. It was great fun! Only one configuration failed to crash the system. (It was also a fun use of code coverage*.)
...
by Brian Marick ;
Likes: 0
Replies: 1
Boosts: 0