Marc:
I've just changed the UserAgent string to be Mozilla and now I see the login
box.  Let me see if I can get the test case to work.

cheers,
Terry


Terry Jennings wrote:
> 
> [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-tp20257006p20306452.html
Sent from the WebTest mailing list archive at Nabble.com.

_______________________________________________
WebTest mailing list
WebTest@lists.canoo.com
http://lists.canoo.com/mailman/listinfo/webtest

Reply via email to