[ Home  |  FAQ-Related Q&As  |  General Q&As  |  Answered Questions ]


    Search the Q&A Archives


When does software-testing finish?

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)

Question by Leanne
Submitted on 4/14/2004
Related FAQ: comp.software.testing Frequently Asked Questions (FAQ)
Rating: Rate this question: Vote
When does software-testing finish?


Answer by RandomAngel
Submitted on 4/18/2004
Rating:  Rate this answer: Vote
Depends on the software being tested, the purpose of the software, and the complexity of the software.  The time of year can also affect the testing phase (software often has its testing time cut in November-December in order to have the software available for Christmas).

On-line Games, for example, are very complex and difficult to make.  Testing can sometimes take around a year.  Simple word processors may take a week to test, however.  It all depends on how many things can go wrong (the more complex, the more things to test).  It's always possible that testing times will get cut short, as well.

Furthermore, it's impossible to find every bug in the program no matter how much testing you do.  In that sense, the testing phase never really ends.

 

Answer by KrishnaKishore
Submitted on 5/18/2004
Rating:  Rate this answer: Vote

Software Testing is finished

1) Test case certain percentage is passed.

2) code review and functionality meets certain specification

3) test budget is completed.


 

Answer by Manoj Bhalerao
Submitted on 6/27/2004
Rating:  Rate this answer: Vote
Software testing finishes when the risk involved in releasing the product are thought to be correctly estimated. These estimates can be done based on quality factors and affordable risk values for each of them.

 

Answer by bg
Submitted on 1/13/2005
Rating: Not yet rated Rate this answer: Vote
It never ends.  Testing takes place in continuous cycles.

 

Answer by Pradeep
Submitted on 1/18/2005
Rating: Not yet rated Rate this answer: Vote
Software Testing should be a continous process. That means it should not begin after the implimentation. Testing should start along with the coding itself. So this idea can make basic testing finish by the scheduled time. And other defects if any will always be very minor and may not cause any notified harm.

 

Answer by sangi
Submitted on 3/4/2005
Rating: Not yet rated Rate this answer: Vote
software testing is finished:
When the budget is depleted
when bug rate falls below a certain level
When dead lines loom
when beta period ends

 

Answer by k.suresh naidu
Submitted on 4/3/2006
Rating: Not yet rated Rate this answer: Vote
we can say testing is fnished if and only if
1)when the bug is free
2)code review and functionality meets certain specifications

 

Answer by heavens
Submitted on 3/16/2007
Rating: Not yet rated Rate this answer: Vote
answer rating is good

 

Your answer will be published for anyone to see and rate.  Your answer will not be displayed immediately.  If you'd like to get expert points and benefit from positive ratings, please create a new account or login into an existing account below.


Your name or nickname:
If you'd like to create a new account or access your existing account, put in your password here:
Your answer:

FAQS.ORG reserves the right to edit your answer as to improve its clarity.  By submitting your answer you authorize FAQS.ORG to publish your answer on the WWW without any restrictions. You agree to hold harmless and indemnify FAQS.ORG against any claims, costs, or damages resulting from publishing your answer.

 

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

 

<< Back to: comp.software.testing Frequently Asked Questions (FAQ)


[ Home  |  FAQ-Related Q&As  |  General Q&As  |  Answered Questions ]

© 2008 FAQS.ORG. All rights reserved.