...The real problem isn't writting bug free code, but writing code that works with everyone else's buggy code (graphics/sound drivers, Direct X, Windows etc.). To test that VSTEP needs their code running on as many machines as possible.
Cheers.
Hi Keith,
That is true; it might have saved some trouble if the betas were tested on average systems.
An open beta is not feasible because signed non-disclosure agreements are required of all testers. This restricts the choice to candidates of an age where such agreements are legally binding.
Too much proprietary information is exposed to make it a good idea. Even with the limited number of testers, copies of betas found their way onto the Internet.
Also, the problem was not that there were undiscovered bugs. The problem was a commitment to the publisher to release on a certain date, ready or not.
As one who studies the bug tracker daily, I can assure you that bugs are found. The problem, as you know, is in fixing them without creating new bugs. This requires complete retesting of the entire program, not just spot testing to see if a particular bug was fixed.
Unfortunately, unless the temptation to add features that have been demanded is resisted, the potential for introducing even more bugs is even higher.
Regards,
Marty
