Xref: utzoo comp.os.misc:1473 comp.lang.c:35268 comp.software-eng:4632 comp.unix.misc:826 comp.unix.programmer:844
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!hp4nl!star.cs.vu.nl!beugel
From: beugel@cs.vu.nl (Beugel Berend Jan)
Newsgroups: comp.os.misc,comp.lang.c,comp.software-eng,comp.unix.misc,comp.unix.programmer
Subject: Book and article references on library verification wanted.
Keywords: Functional testing, module testing, verification, Amoeba, Unix, C.
Message-ID: <8761@star.cs.vu.nl>
Date: 16 Jan 91 15:35:00 GMT
Sender: news@cs.vu.nl
Lines: 26

Hi,

I am looking for references on books and articles on software testing and
verification.
I am currently involved in testing the programming interface of the Amoeba
distributed operating system. The interface simply consists of several
libraries. Most of the programming for Amoeba is done in C.
Testing and verifying the interface would be very similar to testing the
Unix libraries.
Most of the books I found on software testing and verification deal with
the verification of big software systems such as databases, accounting
programs etc. The books on module testing deal mostly with structural testing
where the test programmer has access to the sources of the programs or
functions to be tested.
What I need is references on pure functional testing where all the test
programmer has, is the manual pages for the functions to be tested. He has to
verify that the functions behave as specified in the manual.
This kind of testing is generally done "ad hoc". There seem to be no formal
methods and CASE tools general enough to cover this kind of testing for
operating systems such as Unix. Maybe I am wrong. If so, how is it done in
Unix?

Any ideas? Mail them to beugel@cs.vu.nl.
I can summarize the responses if others are also interested.

Berend Jan Beugel (beugel@cs.vu.nl).