| |
| |
More Resources
Some mistakes are made so often, so repeatedly,
by so many different people, that they deserve the label Classic Mistakes.
More...
Here are a few things to think about
when coding your error-handling routines and designing your error messages.
More...
|
|
|
| |
Have Something
to Share
software testing tip, interesting bug, or had an
interview lately?
Send us an Email.
|
|
|
| |
Promote Your
Products or Services
Interested in promoting your products on
SQAtester.com?
If so, we think you'll like
our Product Storefront Program.
The concept is simple.
More...
|
|
|
| |
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...
|
|
|
| |
Software Team
Solutions That Fit.
Managed well, training is an effective
and simple way to improve organizational results, capabilities and personnel motivation. More...
|
|
|
|
|
|
One of the most important (and most common) things
an SQA Engineer does is to write "bug reports". How well you report a bug directly affects how likely
the programmer is to fix it. You should spend a minimum of time needed to describe a problem in a way that maximizes
the probability that it will be fixed. The content and manner of your reports affect that probability.
|
| How to Write a Fully Effective Bug Report |
 |
___________________ |
|
To write a fully effective report you must:
- Explain how to reproduce the problem - Analyze the error so you can describe it in a minimum number of steps.
- Write a report that is complete and easy to understand.
Write bug reports immediately; the longer you wait between finding the problem and reporting it, the more likely
it is the description will be incomplete, the problem not reproducible, or simply forgotten.
Writing a one-line report summary (Bug's report title) is an art. You must master it. Summaries help everyone quickly
review outstanding problems and find individual reports. The summary line is the most frequently and carefully
read part of the report. When a summary makes a problem sound less severe than it is, managers are more likely
to defer it. Alternatively, if your summaries make problems sound more severe than they are, you will gain a reputation
for alarmism. Don't use the same summary for two different reports, even if they are similar. The summary line
should describe only the problem, not the replication steps. Don't run the summary into the description (Steps
to reproduce) as they will usually be printed independently of each other in reports.
Ideally you should be able to write this clearly enough for a developer to reproduce and fix the problem, and another
QA engineer to verify the fix without them having to go back to you, the author, for more information. It is much
better to over communicate in this field than say too little. Of course it is ideal if the problem is reproducible
and you can write down those steps. But if you can't reproduce a bug, and try and try and still can't reproduce
it, admit it and write the report anyway. A good programmer can often track down an irreproducible problem from
a careful description. For a good discussion on analyzing problems and making them reproducible, see Chapter 5
of Testing Computer Software by Cem Kaner.
The most controversial thing in a bug report is often the bug Impacts:
Low, Medium,
High, and Urgent. Report should show the priority which you, the bug submitter, believes to be appropriate
and does not get changed.
 Share your thoughts on Bugs and Fixes in SQAtester Group.
 E-mail to a Friend.
|
| Books to Read |
|
________________________________________ |
|
|
|
Testing Applications on the Web
Written by a true authority in the field, Hung Q. Nguyen's Testing Applications on the Web is a nicely comprehensive
guide to virtually every conceivable aspect of software testing. It's filled with must-have background information
for any test engineer or manager who's testing thin-client. More...
|
|
|
|
Testing Computer Software, 2nd Edition
The original printing of Testing Computer Software set the standard for the emerging field of test engineering
with a full tour of the state of the art in managing the testing process. The reissued text makes this classic
out-of-print text available once again. Though it relies heavily on older. More...
|
| 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... |
|
|
