Xref: utzoo news.groups:23006 comp.misc:9817 comp.software-eng:4055 Path: utzoo!mnetor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!motcid!ashbya From: ashbya@motcid.UUCP (Adam J. Ashby) Newsgroups: news.groups,comp.misc,comp.software-eng Subject: Re: 2nd CALL FOR DISCUSSION: comp.sw-testing Message-ID: <4424@lava5.UUCP> Date: 15 Aug 90 13:40:32 GMT References: <5459@stpstn.UUCP> Organization: Motorola Inc., Cellular Infrastructure Div., Arlington Heights, IL Lines: 25 In <5459@stpstn.UUCP> cox@stpstn.UUCP (Brad Cox) writes: >In article etxtsg@solsta8.solsta.ericsson.se (Thomas Grennefors TX/DKI) writes: >> >>The purpose of this group will be to discuss software testing. >Please, do not name this group *testing*, as if testing can be >considered in isolation, without regard to *specification*. Why not *testing*, I have been software testing for about nine years now and always managed to include the specifications in my testing. Your high level specification test compiler is still testing. The only other name that I have come across that covers software testing is Software Verification. Comp.sw-testing sounds good to me, you could have a comp.sw-testing.spec-compiler group of course. Please use this as a "YES" vote whenever voting takes place. Adam. -- Adam Ashby | Most, if not all of the above (+1)(708) 632 3876 - work time | came from my mind...and not (+1)(708) 934 1431 - play time | even I have control over ...!uunet!motcid!ashbya | that. - madA 1990