- Title
- Description / Steps errors
- Build number of the product being tested (if necessary also to include the version number and language)
- Recipient of the message
- The importance of
- Attachments with test material (logs, screenshots, memory dumps, etc.)
- Operating system (in most cases, indicating its version, SP or hotfix’a)
Sunday, 22 January 2012
How to Write Bug Report
Labels:
Bug Life Cycle
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment