Tuesday, July 27, 2010

Test Documentation Needed

• Requirement being tested.
• Design verification methodology.
• Code verification methodology.

Document Each Test Case
• Requirement tested.
• Facet / feature / path tested.
• Person & date.
• Tools & code needed.
• Test data & instructions.
• Expected results.
• Actual test results & analysis
• Correction, schedule, and signoff.

No comments:

Post a Comment