| |
| |
Have Something
to Share
software testing tip, interesting bug, or had an
interview lately?
Send us an Email.
|
|
|
| |
Promote Your
Products and Services
SQAtester.com Storefront Program is the best way to help companies promote their products
and services.
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...
|
|
|
| |
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...
|
|
|
| |
Find out which Bug-Track.com account is right
for your software development team, Try our Demo Now!
|
|
|
|
|
 |
|
|
|
|
|
Software Planner:
Project Management / Change Management
and Help Desk Solutions. Free 2 Week Trial.
More...
|
For teams managing software quality, it is crucial
to manage the workflow around the the defect reporting process so that everyone understands how a defect moves
from recognition to resolution. Below are some tips for defining the workflow for software defects.
|
| Managing Workflow for Software Defects |
 |
___________________ |
 |
Define the Workflow Statuses - When tracking software defects, it is important to define
the workflow. Workflow is normally tracked via the "status". Let's create a simple workflow for a development
team, where the tester finds a defect and follows it through resolution, quality assurance and closure. Below are
some possible sets of statuses (workflow) for this process.
Workflow Statuses:
-Active
-Resolved
-QAed
-Committee
-Closed
Flowchart the Workflow - Flowcharting the workflow allows team members to understand
the process in full. We created the flowchart
using Microsoft Word.
Advanced Workflow - In our example above, we used simple workflow. However,
if your team uses software to manage defects, you should be able to implement more robust workflow. For example,
the software should allow you to define "state transitions". This identifies how a status can transition
from one status to another. In our example, above, you may want to setup these transitions:
Active - Can only transition to Resolved or Committee
Committee - Can only transition to Active or Closed
Resolved - Can only transition to Active or QAed
QAed - Can only transition to Active or Closed
Closed - No transitions allowed
Likewise, the software should also allow you to define what fields (or items) you wish to make required upon different
states. In the example above, if the defect is changed to Resolved, we may want to require that the programmer
enter the resolution information (resolution code and description of how they resolved it). Robust defect tracking
software will allow you to define the field attributes for each state transition. Software Planner (http://www.SoftwarePlanner.com) does this nicely, you can see how this is handled from
Software Planner by viewing this movie:
http://www.pragmaticsw.com/GuidedTours/Default.asp?FileName=Workflow
Defect Severity - Another important aspect of defect tracking is to objectively
define your defect severities. If this is subjective, team members will struggle classifying the severity. Below
are severities that are objective:
1-Crash - Set when the defect causes the software to crash
2-Major Bug - Set when there is a major defect with NO workaround
3-Workaround - Set when there is a defect but it has a workaround
4-Trivial - Not a major bug, trivial (e.g. misspelling, etc)
Defect Priority - Similar to severity, the priority for resolving the defect
should be objective, not subjective. Below are priorities that are objective:
1-Fix ASAP - Highest level of priority, must be fixed as soon as possible
2-Fix Soon - Fix once the priority 1 items are completed
3-Fix If Time - Fix if time allows, otherwise, fix in a future release
User Acceptance Test Release Template - Upon entering User Acceptance Testing, it is wise to create
a document that describes how your QA process went. Here is a User Acceptance Test Release Report template:
http://www.PragmaticSW.com/Pragmatic/Templates/UATRelease.rtf
 Share your thoughts on Managing Workflow for Software Defects 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... |
|
|
