Bug Reports - Other Considerations
Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Bug Report @ OneStopTesting
Forum Discription: After Creating the Test Plan, Writing the Test Cases and using them, Finally We need to generate those Bug Reports which Proves that Testers are Good enough & most importantly Indispensable.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=3071
Printed Date: 16May2024 at 5:39am
Topic: Bug Reports - Other Considerations
Posted By: tanu
Subject: Bug Reports - Other Considerations
Date Posted: 20Oct2007 at 12:09am
* If your bug is randomly reproducible, just mention it in your bug
report. But don.t forget to file it. You can always add the exact steps
to reproduce anytime later you (or anyone else) discover them. This
will also come to your rescue when someone else reports this issue,
especially if it.s a serious one.
* Mention the error messages
in the bug report, especially if they are numbered. For example, error
messages from the database.
* Mention the version numbers and build numbers in the bug reports.
* Mention the platforms on which the issue is reproducible. Precisely
mention the platforms on which the issue is not reproducible. Also
understand that there is difference between the issue being not
reproducible on a particular platform and it not being tested on that
platform. This might lead to confusion.
* If you come across
several problems having the same cause, write a single bug report. The
fix of the problem will be only one. Similarly, if you come across
similar problems at different locations requiring the same kind of fix
but at different places, write separate bug reports for each of the
problems. One bug report for only one fix.
* If the test
environment on which the bug is reproducible is accessible to the
developers, mention the details of accessing this setup. This will help
them save time to setting up the environment to reproduce your bug.
* Under no circumstances should you hold on to any information
regarding the bug. Unnecessary iterations of the bug report between the
developer and the tester before being fixed is just waste of time due
to ineffective bug reporting.
|
|