cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berin Loritsch" <blorit...@apache.org>
Subject RE: [CLEANCOON] Let's clean Cocoon and modularize it (was: Cocoon Organization (Cocoon plugins))
Date Tue, 06 Aug 2002 16:30:13 GMT
> From: Torsten Curdt [mailto:tcurdt@dff.st] 
> 
> we have some simple test cases for our transformers. which is 
> basically 
> building a mini pipeline.
> 
>     public void testXXXX() throws CascadingAssertionFailedError {
>         String srcXML = "<root><childs>....</childs></root>";
>         String dstXML = "<root><childs/></root>";
> 
>         assertTransformation(srcXML, new MyTransformer(), dstXML);
>     }
> 
> It would be cool to record a orignial pipeline and save it's 
> states... 
> something like one could mime using the log transformer:
> 
>   <map:generate src="..."/>
>   <map:transform type"log"/> ---> state A
>   ....
>   <map:transform type"log"/> ---> state B
>   
> Then we can pass point A and B to the testcase and see if the 
> behaviour has 
> changed...
> 
> This won't solve all problems... but...
> 
> Just some RT ;-)


What Cocoon needs to test pipelines is an XML Diff utility.  I think
I remember something about such a beast existing, but I have no links
or licensing info.  You need to compare the generated output to the
expected output.  If it is different, it fails the test.


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message