Matt, thank you - but that did not fix my problem. > You could try adding HtmlUnit has a dependency next to webtest - if > the groupId/artifactId matches the dependency in webtest, the newer > HtmlUnit should be used.
I did post to the WebTest mailing list and have gotten back a response that indicates they "may" have WebTest working with HtmlUnit 2.0 soon. http://www.nabble.com/%22missing-%7D-after-property%22-when-testing-page-with-Dojo-initialization.-to16615450.html#a16673159 http://www.nabble.com/%22missing-%7D-after-property%22-when-testing-page-with-Dojo-initialization.-to16615450.html#a16673159 In the meantime, I'm playing around with Selenium (thanks for yor posts last year on this). However integrating the pure HTML tests is no so easy. Not only does it not do I18N, I don't see how to handle symbolics for base URL, etc - I may need to just keep playing. The Selenium-IDE is nice, even if you end up doing some adjustement afterwards by hand. -- View this message in context: http://www.nabble.com/How-to-try-a-more-recent-version-of-HtmlUnit-%28Dojo-errors%29-tp16599498s2369p16678541.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
