Terry, remember that: - verifyText works on the *original* response from server, not the current DOM - WebTest is (too) fast, if your page is modified with a background script (asynchronous XHR, setInterval or setTimeout) you may have to tell WebTest to wait. Unless setInterval is used, the best way to do it is to set <config easyajax="true"/>
Cheers, Marc. -- Web: http://www.efficient-webtesting.com Blog: http://mguillem.wordpress.com Terry Jennings wrote: > Ahmed: > Sure. The application I am trying to use is on sourceforge: > http://sourceforge.net/project/showfiles.php?group_id=140317&package_id=160028 > > If you download the 2.0.0-RC1 file, you can unzip/untar. It is completely > self-contained. I am trying to write a test to get through the login > sequence and to the main page. > > Terry > > > Ahmed Ashour wrote: >> Dear Terry, >> >> Can you post the application URL and your test scenario, so we can >> investigate? >> >> Ahmed >> >> ________________________________ >> From: Terry Jennings <[EMAIL PROTECTED]> >> To: [email protected] >> Sent: Friday, October 31, 2008 9:24:36 PM >> Subject: [Webtest] Javascript adding <div> s to page >> >> >> [resending to see if there is a problem with the mailing list.] >> >> I've just started using webtest and this may be a simple error on my part. >> >> I have searched the forum and found other posts about this issue, but no >> answer. >> >> I am trying to create a webtest for an application I don't own. It looks >> to >> be a GWT application based on tags in the page. There is a >> javascript-based >> button (table with tr/td and onClick()) that I click with <clickElement>. >> Webtest traces say that "[clickElement] INFO >> (com.canoo.webtest.engine.WebClientContext) - Content of window changed >> with >> javascript, it will NOT become current response". >> >> Using firebug in a browser, I see a login "Window" pop up that is actually >> a >> new div that has been added to the DOM. In firebug, I can see class >> names, >> text, etc. In webtest, I cannot locate these elements using xpath. >> >> The login window contains username and password fields I need to populate, >> then click on a login button. >> >> The webtest report succeeds on the clickElement, but fails to find the new >> DOM items for instance, using <verifyText>. The result page on the failed >> step has the original response, not the marked-up from Javascript >> response. >> >> Can anyone help? >> thanks, >> Terry >> -- >> View this message in context: >> http://www.nabble.com/Javascript-adding-%3Cdiv%3E-s-to-page-tp20257006p20257006.html >> Sent from the WebTest mailing list archive at Nabble.com. >> >> _______________________________________________ >> WebTest mailing list >> [email protected] >> http://lists.canoo.com/mailman/listinfo/webtest >> >> >> >> >> > _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
