On 4/27/06, James Mitchell <[EMAIL PROTECTED]> wrote: > With the move to Maven, the taglib tests were pretty much broken and > neglected. They were not neglected due to a lack of interest, but > more for technical reasons (translated -- I didn't know how to force > Maven to do what I wanted). > > So, now here we are with Maven 2, and cactus testing doesn't seem to > be any easier that with Maven 1 and so I am wondering if it isn't > worth taking a look at that idea again. I'd be willing (as I was > back when I wrote the 1,000s of taglib tests) to do all the work on > this.
Not to discourage you at all from adding additional kinds of tests, but I'm not quite ready to throw out the Cactus tests for Taglib. Sandbox them, maybe, though. :) Those tests worked for me in mid-January under Maven 1. (After Laurie fixed them, IIRC.) I think something in the code reformatting broke them, but I haven't had a chance to try reverting to various revisions to find out what happened. (And the Cactus team does plan to finish the Maven 2 plugin, at which point running the tests will be easier. I was over there helping with the Cargo integration recently.) In any case, I'm all for more automated testing, and I'm willing to help. I know there are Canoo WebTest files for (at least) Mailreader, somewhere. (Sandbox?) And last night Don looked at the HtmlUnit tests I've been using to verify that all of the apps will start and display the default page, so I'll add those under action/integration. > Not sure which approach would be best, maybe I'll put together a > proof of concept and send it around for comments. > > What do you think? Sounds great to me. :) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
