| |
| |
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!
|
|
|
| |
Learn more material at a Fraction of Price!
Get the training that will help you
face the challenges and meet the demands of today's competitive market place.
Programs
Offered: Oracle DBA, Cisco Networking,
Software Testing & Programming. More...
|
|
|
| |
Advanced bug
tracking system
FREE Try our [ASP Hosted solution] for free for one month, no obligation to pay.
An extremely practical and cost effective Web Based Bug Tracking Software and help desk software ready to be integrated
into company intranet today. More...
|
|
|
| |
TrackStudio allows you to reduce the maintenance cost of managing a large number of projects along with lowering security risks. More...
|
|
|
|
|
SQAtester.com monthly newsletter reaches its
receptive audience directly through. Advertisers
can place their message with a link or banner to their site.
This article talks about the effective methods of writing Defect reports which will be easy for developers to identify
the cause of defect. And by this we can avoid re-work and reduce duplication of defect documents.
|
| Effective methods of writing Defect description
|
 |
______________ |
|
shared by Latharajesh Rajesh
Testing is commonly used to execute software and finding defects. A Defect which describes of any variance or any
discrepancies between actual and expected results in application software. Defects should be documented in such
a way that any developer should understand the defect description and he/she can reproduce in their respective
environment.
Defects can be logged by using Tools like Eg Siebel, Track, PVCS etc….and it can also be logged by documenting
the defects and maintaining the document in repository. Testers should write the defect description efficiently
which will be useful for others within a project. And the documentation should be transparent.
Best Practices of writing defects
descriptions.
· Pre-Requisite of a Defect Document.
· An Abstract of a defect
· Description and Observation of a defect
· Screen shot of a Defect.
Pre-Requisite of a Defect Document
Document should contain few standard details:
- Author Name or Submitter Name
- Type of Defect (Eg: Enhancement, Issue or Defect)
- Submitted Date
- Fixed Date
- Status of the defect
- Project Phase (Eg: version 1.1, 2.0 etc…)
- Version Found (Daily builds)
- Severity (Eg, Critical, major, Minor, Cosmetic)
Abstract of a Defect
Testers should only specify a brief description of a defect
Eg: Unable to update a record
Description and Observation of Defect
In Description column the first few lines should specify an exact problem in the application. And in the following
paragraph mention in detail like steps to reproduce (Eg , Start from the application Logon till the defect was
found in the application).
Following with an Observation like (Eg, System displays an error message Eg: “Unable to update the record “. But
according to functionality system should update the updated record). And it will be great if a tester specifies
few more observation points like:
- This particular defect occurs in a Particular version (Eg Adobe versions for a Report.)
- This particular defect also found in other modules
- Inconsistency of application while reproducing the defect (Eg, some times able to reproduce and sometimes
not)
Screen Shot of a defect
By providing a screen shot along with the defect document it will be very much useful for the developers to exactly
identify the defect and the cause. And will be useful for the testers to verify in future of that particular defect.
Tips for Screen shot:
- Screen shot should be self explanatory
- A Figure like arrow , box or circle can be highlighted (were exactly the problem accrued this type highlighting
will be helpful for GUI / Cosmetic related defects)
- Use different colors for specific descriptions
Conclusion
By giving the brief description of defect the
· Easy to analyze and cause of defect.
· Easy to fix the defect
· Avoid re-work
· Testers can save time
· Defect duplication can be avoided.
· Keeping track for defects
 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... |
|
|
