lotus

previous page: 3.11) What Is Available On Object-Oriented Testing? Courses
  
page up: Object-Oriented Technology FAQ
  
next page: 3.12) What Distributed Systems Are Available? (Object-Oriented Technology)

3.11) What Is Available On Object-Oriented Testing? Software




Description

This article is from the Object-Oriented Technology FAQ, by Bob Hathaway rjh@geodesic.com with numerous contributions by others.

3.11) What Is Available On Object-Oriented Testing? Software

There is a smalltalk class library in the Univ. of Illinois archives
which includes a simple Tester class written by Bruce Samuelson
(bruce@utafll.uta.edu). It is a general superclass for application
specific classes that test non-interactive objects such as trees,
collections, or numbers. It is not suitable for testing user interface
components such as windows, cursors, or scroll bars. The filein
includes Tree classes, Tester itself, and subclasses of Tester that are
used to validate the Tree classes. For ParcPlace Smalltalk (ObjectWorks
4.1 and VisualWorks 1.0). To get it ftp the file
"/pub/st80_vw/TreeLW1.1" from st.cs.uiuc.edu.

IPL Ltd. (in the UK) has a testing tool called Cantata which allows for
testing C++, but as far as I am able to determine, it has no special
features for C++ testing. From the product literature:
Cantata allows testing to be performed in an intuitive way
making the tool exceptionally easy to use and productive in
operation. Cantata is suitable for testing software written in
either C or C++.

Cantata provides comprehensive facilities for all forms of
dynamic testing, including: functional testing, structural
testing, unit testing and integration testing. Cantata has been
specifically designed to operate in both host and target
systems and so allow full portability of tests between these
environments.
For more information contact IPL:
IPL Ltd.
Eveleigh House, Grove Street,
Bath BA1 5LR
UK
(0225) 444888
(0225) 444400 (FAX)
email: shaun@iplbath.demon.co.uk

TestCenter from CenterLine will do coverage testing of C++ (and C)
code. Also does some memory debugging (similar to Purify) and regression
testing. Highlights from CenterLine literature:
*Automatic run-time error-checking on executables to enhance quality
*Automatic memory leak detection on executables to optimize memory use
*Graphical test coverage to highlight any code not executed during test runs
*Intuitive GUI for easy test analysis
*Programmatic interface to output files and cumulative code coverage
to support batch-mode and regression testing
*No recompilation needed, resulting in quick turnaround
*Complete C and C++ language support
*Integration with leading programming tools for maximum productivity gains

MicroTech Pacific Research (mpr.ca) has a C++ class testing tool called
ACE (Automated Class Exerciser) which is available under non-disclosure
agreement. It is not currently for sale. If you are interested,
contact Paul Townsend, townsend@mprgate.mpr.ca.

Software Research Inc. (625 Third St, San Francisco, CA 94107-1997,
voice: 1-415-957-1441, email: info@soft.com) has a coverage tool for C++
that is called tcat++. It is an extension of SRI's tcat program.

Quality Assured Software Engineering (938 Willowleaf Dr., Suite 2806,
San Jose, CA 95128, voice: 1-408-298-3824 ) has a coverage tool for
C and C++ called MetaC. It also dones some syntax checking and memory
allocation checking.

A group of volunteers is building a C++ test harness for the automated
testing of C++, C and Perl programs. The system is called ETET (Extended
Test Environment Toolkit). To join the group of volunteers, send email to
etet_support@uel.co.uk
The software is available via anonymous FTP from bright.ecs.soton.ac.uk
(152.78.64.201) as "/pub/etet/etet1.10.1.tar.Z". They are looking for
other FTP sites - sned email to the above address if you can provide
one. This is a beta release and _should_ compile on any POSIX.1 system.
As much of this work is being done by SunSoft, my guess is that the
software will have the fewest problems on SunOS or Solaris releases.

> ACKs

Thanks to the following for helping assemble this list:
Benjamin C. Cohen, bcohen@scdt.intel.com
Brian Marick, marick@hal.cs.uiuc.edu
Bruce Samuleson, bruce@utafll.uta.edu
Daniel M. Hoffman, dhoffman@uvunix.uvic.ca
Edward Klimas, ac690@cleveland.freenet.edu
John Graham, J.Graham@axion.bt.co.uk
Jim Youlio, jim@bse.com
Jeffery Brown, jeffrey.brown@medtronic.com
Lars Jonsson, konlajo@etna.ericsson.se
Manfred Scheifert, ch_schie@rcvie.co.at
Mark Swanson, mswanson@mechmail.cv.com
Mary L. Schweizer, mary@gdwest.gd.com
Michael Einkauf, Michael_Einkauf@iegate.mitre.org
Paul Townsend, townsend@mprgate.mpr.ca
Phyllis G. Frankl, pfrankl@polyof.poly.edu
Rachel Harrison, rh@ecs.soton.ac.uk
Risto Hakli, rkh@tko.vtt.fi
Russ Hopler, russ@bse.com
Stephane Barbey, barbey@di.epfl.ch
Tony Reis, tonyr@hpsadln.sr.hp.com
Yawar Ali, yali@bnr.ca

 

Continue to:













TOP
previous page: 3.11) What Is Available On Object-Oriented Testing? Courses
  
page up: Object-Oriented Technology FAQ
  
next page: 3.12) What Distributed Systems Are Available? (Object-Oriented Technology)