Answer Posted / parul gupta
Testing is potentially endless. We can not test till all
the defects are unearthed and removed -- it is simply
impossible. At some point, we have to stop testing and ship
the software. The question is when.
Realistically, testing is a trade-off between budget, time
and quality. It is driven by profit models. The
pessimistic, and unfortunately most often used approach is
to stop testing whenever some, or any of the allocated
resources -- time, budget, or test cases -- are exhausted.
The optimistic stopping rule is to stop testing when either
reliability meets the requirement, or the benefit from
continuing testing cannot justify the testing cost. This
will usually require the use of reliability models to
evaluate and predict reliability of the software under
test. Each evaluation requires repeated running of the
following cycle: failure data gathering -- modeling --
prediction. This method does not fit well for ultra-
dependable systems, however, because the real field failure
data will take too long to accumulate
| Is This Answer Correct ? | 2 Yes | 0 No |
Post New Answer View All Answers
Can you explain the elementary process?
Can anybody write the test cases for the following scenario. I want to create District. for that, District Code field, District Name field, Reset button, Submit button, Back button are there in the screen. whenever we enter District Code & District Name in the related fields, by clicking on Submit button, District should be created. By clicking on Reset button, all fieds should be cleared. By clicking on Back button, user should navigate to home page. Can you write the test cases for the scenario. I want to know the test case format for the scenario. what procedure is the best. tahnks in advance...
I have 2 years of exp. in testing and looking for a change if any body knows, about any vacancy in testing then plz contact me on deepti_ac@yahoo.co.in
what is the use of l10n testing?
What are the different cost elements involved in implementing a process in an organization?
hai friends, I need clarifications for some doubts in testing terminology. 1.What is thread testing. 2.What is bucket testing and which automated tool is used to do this test. 3. ERP testin automation testing. 4.What is Data Warehousing testing? 5.What is Implementation testing? 6.What is Shake out testing? please let me have the clarifications in detail
According to RBI rule how much money can be transferred through online banking at one time...?
How would you test a service oriented architecture (soa) web application?
Can you explain requirement traceability and its importance?
Explain the procedure & path of s/w in testing?
What are the various techniques in white box testing?
When did u complete testing ? Which scenrio should not be in automation testing ? why ?
Why would we not include these?
Can you explain the workbench concept?
wat is meant by frontend and backend testing
