home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!icd.ab.com!iccgcc.decnet.ab.com!kambic
- From: kambic@iccgcc.decnet.ab.com (Bonus, Iniquus, Celer - Delegitus Duo)
- Newsgroups: comp.software-eng
- Subject: Re: Test Completion Criteria
- Message-ID: <1992Nov20.102710.9319@iccgcc.decnet.ab.com>
- Date: 20 Nov 92 10:27:10 EST
- References: <1efq9dINN5ps@griffin.orpington.sgp.slb.com>
- Lines: 32
-
- In article <1efq9dINN5ps@griffin.orpington.sgp.slb.com>, monteiro@edda.nl (Francisco Monteiro,207) writes:
- > One of the most difficult question to answer when testing a program is
- > determining when to stop, since there is no way of knowing if the error
- > just detected is the last remaining error. What criteria is the common for
- > industry, as the ones i know of are both meaningless and counterproductive.
-
- Be interested in the ones you ahve seen.
-
- > If anybody has experiance please reply to net.
-
- Sure. Testing is done when I say it is done. (8:-))
-
- Testing is done when:
- The cost of fixing the last error os greater than the
- cost of creating a new release, testing, releasing, and installing it.
-
- The measured number of errors equals the historically predicted number of erros
- for the type of application under development.
-
- Coverages agreed to in advance for unit, integration, functional, and systems
- testing are all achieved, while the bumber of errors detected remains below the
- cost/benefit line of resolution before release.
-
- You tested what you agreed to test.
-
- etc.
-
- There are more that others will no doubt be adding to this list.
-
- George Kambic
- sd
-
-