Slashdot Mirror
Document Formats For Software Release Manifests?
Lt. Wuff asks: "I work in the QA/testing realm. My second biggest headache (QA being treated like the unwanted bastard child of software development being the biggest) is poor documentation of a given deliverable. If I don't know what's coming, I really can't plan the testing. Along the same lines, there really needs to be a way to get a quick glance at a release and know where it's at and what it's doing. Release notes tend to chase the development and are only somewhat useful for test planning. I'm not sure home many people here use something like a release contents document in their development/testing cycle, but I'm a huge fan of using them to control scope, manage expectations and allow me to plan testing. It's a quick glance at the release that anyone can understand. I've got a pretty bland format that assumes that the people are using some issue tracking software and I'm looking for others (i.e. developers) who use something like this to share ideas with."
Sorry, but you must now cease and decist. DoubleClick already holds the patents for both bland formats and tracking software.
A simple Google search yeiled some pretty good results, perhaps some /. readers have used some of that software. It seems like there is an abundance of it out there. What kind of QA do you do exactly, and what kind of software is it? Perhaps there is a package specificly aimed at one area, such as game design or office software.
"Everything that can be invented has been invented."
--I assume full responsibility for my actions, except the ones that are someone else's fault.