|
From: Tony R. <ton...@pr...> - 2002-07-31 07:35:08
|
Sounds like a good plan Sean. -----Original Message----- From: xpi...@li... [mailto:xpi...@li...]On Behalf Of Sean McGrath Sent: 30 July 2002 20:11 To: xpi...@li... Subject: RE: [Xpipe-developers] I see the light or do I? [Tony Redmond] > > For example, a unit test may consist of a DTD > > that validates the input to a unit test and a DTD that > > validates the output of a unit test. The unit test itself > > calls the XComponent to which the unit test is attached. I have a suggestion for how the unit test "calls" the XComponent. The unit testing framework creates an XPipe on the fly - of length 1 - the XComponent to be tested. It then invokes the XPipe engine feeding it the test inputs and checking the real test outputs against the desired outputs. In other words, the Unit testing framework sits on top of the XPipe engine. One engine two environments - unit test (developer), real user files (user). How does that sound? ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ Xpipe-developers mailing list Xpi...@li... https://lists.sourceforge.net/lists/listinfo/xpipe-developers |