Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!lupine!rfg
From: rfg@NCD.COM (Ron Guilmette)
Newsgroups: comp.lang.c++
Subject: Re: C++ testing at CADRE Technologies
Keywords: C++, CADRE Teamwork, Project Experience, Testing
Message-ID: <1670@lupine.NCD.COM>
Date: 21 Sep 90 02:28:46 GMT
References: <1985@ztivax.UUCP>
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 31

In article <1985@ztivax.UUCP> sof3@ztivax.UUCP (Oliver Rothe) writes:
<
<I just have heard about CADRE Technologie and their product Teamwork (TM).
<( perhaps you've never heard about it; it belongs more to the Ada universe
<  and seems to be a great Analysis/Design tool - C++ support is planned ).
<
<Some newer parts of it were implemented using C++, which was quite successful.
<Reportedly, they also tried to reimplement a large chunk of their software in
<an attempt to lower maintenance cost, but eventually found out that they were
<not able to test it sufficiently ( whatever this means).
<
<So this was a failure. Unfortunately, I have no clue whatever the problem was.
<Could the software not be tested due to non-existing source level debuggers or
<what ?
<Perhaps someone out there could give me a hint. 
<I'm not just curious, but interested in real project experience with C++.

I don't know why a lack of debuggers would be your first guess as to why
a piece of code could not be tested.  That's probably the last thing that
I would have though of.

My first guess would have been a lack of an adequate specification of what
the code was *supposed* to do when it was operating `correctly'.  Obviously,
if nobody knows for sure what it is supposed to do, it's not possible to
verify (through testing or any other means) that it does in fact do what it
is supposed to do.
-- 

// Ron Guilmette  -  C++ Entomologist
// Internet: rfg@ncd.com      uucp: ...uunet!lupine!rfg
// Motto:  If it sticks, force it.  If it breaks, it needed replacing anyway.