| |
| |
See Also
QA and Dev. More...
QA Team Responsibilities. More...
Managing Test Team. More...
Qualities of a Good Tester. More...
To ship the Product. More...
Weekly Status Report
Sample. More...
Stocking and Managing a Test Lab. More...
Key QA Documents. More...
Improving the Quality process by doing
the
Metrics Calculation
Download
Documentation Tips. More...
|
|
|
| |
Try our bug tracking system. We would also appreciate your feedback and comments. More...
|
|
|
| |
Promote Your
Products or Services
Interested in promoting your products on SQAtester.com?
We think our Storefront Program is the best way to help companies promote their products and services. More...
|
|
|
| |
TrackStudio allows you to reduce the maintenance cost of managing a large number of projects along with lowering security risks. 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...
|
|
|
|
|
Manage your bugs
in minutes!
|
|
| |
Are you a new in Software Quality Assurance?
Please let this be a reference to
get you started learning all about SQA. More...
|
|
|
| |
Have Something
to Share
software testing tip, interesting bug, or had an
interview lately?
Send us an Email.
|
|
|
|
|
|
Quality is continuous improvement.
|
| When Project is Done |
 |
_________________________________ |
|
When your project is done (this generally is when the
product has gone to "FCS"
(has been shipped to the first customer as released product), there are some special things that the QA Lead should
do with respect to the project.
-Close Bugs:
All bugs resolved with this project's release must be put into the
"Closed" state and marked as "Fixed", Rejected, or "Accepted" in this
release.
Do these by following steps:
1.Decide on the unique string that will distinguish the bugs
resolved by this release from those resolved in previous and future
releases. This string typically should include the Product and the Version # the project is released as, except
if the project was a follow-on project with
the same version number as another product only released later in which case the Product should not be used but
the platform info should be used instead.
For example:
[Product Name] [Ver 3.0]
2.1 ASCII
2.1 PC
[Product Name] [Ver 3.0.5]
It is strongly recommended that the string utilize the actual 'Version #' the product is released as rather than
the internal project name so that the name will make sense to people who are not familiar with the internal project
names.
2.Ensure that bugs already closed for this release have the
'Resolved in Version' status set to this string. It is very likely that some
other string was used when resolving bugs during the project, so probably all of the bugs closed in connection
with this release need to be modified by
this step.
3.Bugs that were fixed or rejected in this release but not yet closed need to be changed to the 'Closed' state.
Fixed bugs are most likely ones that were not verified as fixed by QA, rejected bugs were not verified as rejected
and Accepted bugs are most likely ones that were not verified as acceptable to leave open, so to close them you
most likely have to indicate: "Bug Report Diary"' to indicate what changes you are making to a bug 'Resolved
in Version' - <the unique string decided above in step (1)>, and finally, 'QA Status - Complete'.
NOTE: At the end of a project, most of the bugs that are In QA are likely LOW or MEDIUM in
priority because part of the criteria of a project reaching FCS is for all URGENT, HIGH, and
50% of MEDIUM priority bugs to be verified by QA. Therefore, usually there are not many URGENT or HIGH bugs left
to verify at FCS. If there are URGENT or HIGH bugs that are still unverified, it is suggested to assign these to
QA engineers for formal verification and not to simply set the 'Verified' field to "No" for these bugs.
"OAR" Bugs (Open at Release)
Change any bugs flagged as "Open at Release" to "Unspecified" so they will be examined for
the next project.
General Clean-up
You may also do any general "clean-up" of bugs related to this project. Some such clean-up could be to
fix problems where too many bugs were submitted with 'Problem Area' is not specified or where the Bug Priority
was not being set properly to the Pre-Alpha/Alpha/Beta/Released value. You may also want to check for inconsistencies
that can affect any statistics you or others perform on the bugs for this project.
 Share your thoughts on When Project is Done in SQAtester Group.
 E-mail to a Friend.
|
| Books to Read |
|
________________________________________ |
|
|
|
Landing the Job You Want
You've looked at dozens of books that promise to help you get a job. This book is different. This book is written
by an executive whose business is teaching managers how to interview job candidates. He knows what they're looking
for--and how you can successfully prepare for landing that job you really want. More...
|
|
|
|
201 Best Questions To Ask On Your Interview
Packed with 201 proven questions, including examples of some of the smartest and dumbest interview questions from
hundreds of recruiters, job coaches, hiring managers, and Fortune 500 human resources professionals, this hands-on
guide gives you the edge you need. 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... |
|
|
