Rank 1
We are trying to WebUI Test Studio for testing our existing solution.
I should say our solution is slightly complex. It's web based. But almost all popup windows is opening in overlay div layers and each layers has iframe for subpage navigation. Allmost similar to RadWindows but our solution older then you :)
IE 8 highlighting tool is working on our normal pages that awesome. But It doesn't work on sub iframes which are opening into overlay div layers on root page.
What should I do for solving this situation ?
3 Answers, 1 is accepted
Thank you for taking the time to evaluate WebUI Test Studio.
I am sorry you have run into this problem. The tool is supposed to work just fine in the scenario you have described. There are no settings to control this behavior. Is there any way we can access your website directly so we can study this problem?
Also, are you trying the QA Edition or the Developer Edition? This post was filed in the WebAii framework forum, which is a .NET programming library only.
Cody
Rank 1
I'm using developer edition, an example project can be found in attachment.
As I said,
Configure attached example project as virtual directory and open default.aspx page on your browser. After than click to Open Window button.
An overlay div will be opened and it contains an iframe that navigate to subpage.aspx when it's document ready.
Try to create a test record from VS 2010 which I'm using it. You will see dom highlighting doesn't work on opened iframe content.
Is it possible to quickly solve this problem ?
Looking forward to hear about this.
Thank you very much for the sample application. Now I see exactly the problem you are dealing with. jQuery is dynamically creating new HTML content and injecting it into the DOM. It appears to not be working because our recording actually runs against a cached copy of the DOM for performance reasons. Since the DOM was dynamically changed by JavaScript (I think you already know jQuery is just a bunch of JavaScript) our cached copy is now stale and out of sync with the real DOM in the browser.
For most web pages this isn't a problem. The browser tells us when the page was changed due to an interaction with the web server. It doesn't though when JavaScript does the updating internally.
Fortunately the cure for this is quite simple. Whenever your overly opens, just click the Reconfigure Browser button as shown in the attached screen shot. That causes us to refresh our copy of the DOM and recording works just fine (until our copy becomes stale again).
I also found that jQuery is putting a dynamically generated ID on the frame nodes. I had to manually delete this property before playback would work right. See the other attached screen shot for details.
Cody