| |
| |
See Also
What is Software Testing? More...
Bug Report Tips. More...
Bug Life Cycle Model. More...
Bug Report Components. More...
List of Test - Reviews
in alphabetical order. More...
|
|
|
| |
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...
|
|
|
|
|
|
Common sense should always have precedence over
this rules. But to have some commonality between assigning bugs priorities, use the following guidelines.
|
| Bug Impacts |
 |
__________________________________________ |
 |
Low impact
This is for Minor problems, such
as failures at extreme boundary conditions that are unlikely to occur in normal use, or minor errors in layout/formatting.
These problems do not impact use of the product in any substantive way.
Medium impact
This is a problem that a) Effects a more isolated piece of functionality. b) Occurs only at certain boundary conditions.
c) Has a workaround (where "don't do that" might be an acceptable answer to the user). d) Occurs only
at one or two customers. or e) Is very intermittent
High impact
This should be used for only serious problems, effecting many sites, with no workaround. Frequent or reproducible
crashes/core dumps/GPFs would fall in this category, as would major functionality not working.
Urgent impact
This should be reserved for only the most catastrophic of problems. Data corruption, complete inability to use
the product at almost any site, etc. For released products, an urgent bug would imply that shipping of the product
should stop immediately, until the problem is resolved.
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... |
|
|