Hi Jason, I can think of 2 ways for doing this:
- xmlunit :-) - using directly Jelly (the xml taglib) as I've done in several plugin tests. It won't test the full generated XML (is that necessary? I don't think so) but only the "important" parts. -Vincent > -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: 05 January 2004 05:29 > To: Maven Developers List > Subject: xml unit testing > > Howdy, > > I know that XmlUnit exists but does anyone have any recommendations for > xml unit testing tools? A lot of the plugins generate xml and I want to > improve the testing across the plugins so I figure with a good xml unit > testing tool I can probably make a start at plugin tests for many of the > plugins missing tests. > > ./ant/src/plugin-test > ./aspectwerkz/src/plugin-test > ./changes/src/plugin-test > ./checkstyle/src/plugin-test > ./clean/clean/src/plugin-test > ./clean/src/plugin-test > ./clover/src/plugin-test > ./dashboard/src/plugin-test > ./deploy/src/plugin-test > ./dist/src/plugin-test > ./ear/src/plugin-test > ./faq/src/plugin-test > ./gump/src/plugin-test > ./html2xdoc/src/plugin-test > ./java/src/plugin-test > ./plugin/src/plugin-test > ./war/src/plugin-test > ./xdoc/src/plugin-test > > That's all we have which I will take a stab at improving tomorrow. I > hope to make a shell of a little tool, a harness of sorts, for testing > plugins independently across various versions of maven. > > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.org > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
