Linked by Flatland_Spider on Wed 1st Oct 2008 00:05 UTC
Thread beginning with comment 331995
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: Trying to read the article
by jayson.knight on Wed 1st Oct 2008 05:35
in reply to "Trying to read the article"
There is also a debugging tool that is meant to capture enough system and application state from the testers to get all the information to reproduce bugs. Eliminating the "No-repro" bugs, in the parlance they just made up. This one might actually be pretty cool, as long as you have enough of a bull shit detector to realize that it probably won't eliminate non-reproducible bugs like they claim.
No automated piece of software will ever capture as much useful information as a good QA department.
RE[2]: Trying to read the article
by evangs on Wed 1st Oct 2008 05:54
in reply to "RE: Trying to read the article"






Member since:
2006-10-01
First, I suggest anyone reading the article just skip the bullet points. It sounds like it was run through the buzz word generator. http://pdos.csail.mit.edu/scigen/
On the whole it is very light on real content. It looks like they added a UML graphing utility that the pointy haired boss can fiddle with. It says that it is to 'enable users', but the users aren't going to care. Most of the time programming is just black magic as far as they care.
There is also a debugging tool that is meant to capture enough system and application state from the testers to get all the information to reproduce bugs. Eliminating the "No-repro" bugs, in the parlance they just made up. This one might actually be pretty cool, as long as you have enough of a bull shit detector to realize that it probably won't eliminate non-reproducible bugs like they claim.