Re: test suite generation for Fortran compiler testing

henry@spsystems.net (Henry Spencer)
11 Dec 2004 12:25:55 -0500

          From comp.compilers
Related articles
test suite generation for Fortran compiler testing gauravga@noida.hcltech.com (Gaurav Gautam, Noida) (2004-11-20)
Re: test suite generation for Fortran compiler testing arargh411@arargh.com (2004-11-26)
Re: test suite generation for Fortran compiler testing gah@ugcs.caltech.edu (glen herrmannsfeldt) (2004-11-26)
Re: test suite generation for Fortran compiler testing beliavsky@aol.com (2004-11-26)
Re: test suite generation for Fortran compiler testing nmm1@cus.cam.ac.uk (2004-11-29)
Re: test suite generation for Fortran compiler testing henry@spsystems.net (2004-12-11)
Re: test suite generation for Fortran compiler testing henry@spsystems.net (2004-12-11)
Re: test suite generation for Fortran compiler testing nmm1@cus.cam.ac.uk (2004-12-16)
| List of all articles for this month |
From: henry@spsystems.net (Henry Spencer)
Newsgroups: comp.compilers
Date: 11 Dec 2004 12:25:55 -0500
Organization: SP Systems, Toronto, Canada
References: 04-11-086 04-11-093 04-11-125
Keywords: Fortran, testing
Posted-Date: 11 Dec 2004 12:25:55 EST



Nick Maclaren <nmm1@cus.cam.ac.uk> wrote:
>That myth about needing to exercise every code segment has been
>around for at least 35 years but, like all good myths, tramples
>ruthlessly on the actual facts...


It's not a myth; it's merely not the whole story. Path coverage
testing and statement coverage testing are two different things. Path
coverage testing is *better*, but it's also rather harder to do.
Statement coverage testing isn't as good, but it's a lot better than
nothing and it finds a lot of bugs.
--
"Think outside the box -- the box isn't our friend." | Henry Spencer
                                                                -- George Herbert | henry@spsystems.net


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.