-----Original Message----- From: Brandon Moore [mailto:bmo...@commcode.com] Sent: Thursday, July 10, 2003 3:27 PM To: webt...@lists.canoo.com Subject: RE: [Webtest] Upgrading webtest build265 to build307

I'm guessing the rest of the error message was something to the effect of "must have type Task, actual type UnknownElement"?

You need to change the taskdef. The example on the website has been updated. You need the file webtestTaskdefs.properties which should be included in the build. It wasn't in 284, which was the latest packaged build I downloaded, but I think it has been added since then.

Every step needs to be defined as a separate ant task now. This was done so you can extend webtest by writing a new task that implements the appropriate interfaces from webtest (descended from the ones in ant) and registering it with ant, rather than rebuilding webtest. This means the containers like <steps> and <not> are now TaskContainer rather than simple elments, so the error messages changed.

With this change, it might be possible to split one test between targets, or to interleve other ant tasks with webtest steps. Both would probably require some tweaks to the code, though.

I would like to split out reusable chunks of test steps into ant targets. Using entity references works, but parameter handling is awkward, and I can't use <script> tasks to work with them. It would be really cool if the test suite I'm building could be as easy to extend as a junit test suite.

Hope I solved the right problem here.