Mailing-List: contact general-help@xml.apache.org; run by ezmlm
From: David_Marston@lotus.com
Subject: Re: Test Infrastructure Project Proposal
To: general@xml.apache.org
Message-ID: <OF5B3BB85E.115081D5-ON852569EF.007C33D4@lotus.com>
Date: Sat, 10 Feb 2001 17:49:17 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii


Scott Boag wrote:
>What is happening in the XML/Web world is the integration of a lot of
>smaller components, plugged together via (hopefully) standard interfaces.
>This increases the need for unit testing, and integration testing in a
>big way.  In systems such as we are building, robustness is everything,
>and fragility is becoming an increasing problem.

This looks like a good topic for a workshop at ApacheCon. One of the
most intriguing aspects of this integration testing is governing how
various modules get plugged in. For example, the Xalan team would like
to have a complete pipeline of Apache software that works, then plug in
a revised Xalan piece, holding all other pieces constant, and see if the
pipeline still works. I'm sure that other projects would like to do the
same thing.

Similarly, additional test cases can be introduced by attempting to run
them through the pipeline that works. If the test comes out as expected,
then it acquires the status of "worked at least once" that means it can
be applied in a regression scenario, and it might also be an example for
documentation/learning.
.................David Marston