| |
| |
This Newsletter
Brought to You by
The leading web-based task and bug tracking software
for software development and IT! More...
|
|
|
| |
Promote Your
Products and Services
SQAtester.com Storefront Program is the best way to help companies promote their products
and services.
More...
|
|
|
| |
Find out which Bug-Track.com account is right
for your software development team, Try our Demo Now!
|
|
|
|
|
|
SQAtester.com monthly newsletter reaches its
receptive audience directly through. Advertisers
can place their message with a link or banner to their site.
|
| Bug Report Tips |
 |
_______________________________________ |
|
It is really important that the subject of bug/incident
report should help to determine the severity of it rather than a general statement. In the description we should
furnish all the possible information related to the incident including Config/Setup steps, Reproduction Steps,
Current behavior and Expected behavior.
A typical bug report should contain the following mandatory fields
Fields: Example
Incident# : Could be a auto genarated serial #
Product Version: 2.0
Product Module : Web Client
Subject : Newly created reports cannot be opened
Status : New, Q/A, Dev, Closed, Reopen, Rejected, Not Reproducible:
Severity : S0, S1 etc..
RequestID : person who log the bug (Q/As, Clients)
AssignedID : person who should work on it (Development, Q/A)
ChangedID : person who chahge the record at last
by Rajendrakumar Kankani
I would like to say something about Reporting A Bug.
As said, "WYSIWYG" (What You See Is What You Get). When you report a BUG you need to very very specific
about the description of the BUG. You need to give as much information as possible about the BUG. Give the BUG
a "Title", "Area where affects", "The Description", Severity", "Priority"
and the most important thing "The Repro Steps". A common term used in MICROSOFT is something called as
a "QUALITY BUG". Microsoft terms something as a Quality Bug, "If its reproduced without any extra
inputs from the person who has filed the bug". This means that if you are totally specific and crystal clear
in your description of the BUG, and that doesnt require you to further give any inputs at the client place when
being reproduced, then that is a Quality Bug. Though not restricted with the name at Microsoft, Quality Bug can
also be something related to the Quantitative effect that has on the application under test. If the application
crashes or some major functionality is disturbed/affected, then that can be termed as a Quality Bug.
by Mantrala Kiran Kumar
 Share
the Experience and Exchange Ideas
in SQAtester Group.
 E-mail to a Friend.
We at SQAtester.com, look forward to building a lasting, creative, and friendly relationship with our community.
Good luck, and happy Joining!
|
| Categories |
|
________________________________ |
| Community |
|
________________________________ |
| Specials |
|
__________________________________ |
| Millions of titles discounted up to 40-90% off. Great
low prices on your favorite books. More... |
|
Find all of your favorite software.
More... |
|
|
