Hi Lynn,

normally you can call ant (the entry point is tests' parent directory).
Personally this is what I do but if for some reasons your ant
installation contains some exotic stuff, you may encounter problems like
the one you had. The webtest script just run Ant but ensure that nothing
uncontrolled comes into the classpath.

Cheers,
Marc.
-- 
Blog: http://mguillem.wordpress.com


Walton, Lynn wrote:
> Thanks Mark. Using webtest from that directory instead of ant did the
> trick.  I thought I was reading something recently that said to go to
> the tests directory and run ant, but I can see now it says to run
> webtest.  Maybe I was thinking of what I used to do when I was actively
> using webtest years ago. 
> 
> Thanks again!
> Lynn
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Marc Guillemot
> Sent: Thursday, November 29, 2007 1:25 PM
> To: [email protected]
> Subject: Re: [Webtest] Build 1641 default tests failing
> 
> should really not be a problem.
> 
> I now see that you used the webtest.{sh|bat} script to create the
> project but not to run it after.
> Can you try to call webtest.bat in your project folder? I guess that
> this is a problem with your Ant version as described in
> http://webtest.canoo.com/webtest/manual/troubleshooting.html.
> 
> Cheers,
> Marc.

_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest

Reply via email to