Bret Pettichord ([EMAIL PROTECTED]) typed this ... > At 02:30 AM 7/23/2005, Kurt Sussman wrote: > >I'm trying to write a script that tests a relatively simple web app. > >There are two factors that make this difficult: the page I need to test > >is created by a javascript function (indirectly via a link), and the
Replying to myself... I think the 'attach' method might work for me... I'll check as soon as my test system is available again. http://rubyforge.org/pipermail/wtr-general/2005-June/002142.html > >If the archives were searchable, I'd search them before asking... I hope Thatks for the reminder about google's 'site:' tag. That helped a lot. > This is the biggest weakness with Watir: modal javascript popups. It's not a modal javascript popup; it's a new browser window spawned by a javascript function. The original page goes to a new URL after spawning the new window. > In the mean time, the best we've been able to to do is to send key events > to the popup window to get it to go away. This "solution" is in the FAQ. I don't want the popup to go away. The app I need to test is in it. If I wanted it to go away, the FAQ would probably have gotten me there. Does this clarify the problem I'm having? Do you think the 'attach' method is the right approach? Now I'm trying to get my client to think about giving the testers a direct URL instead of this javascript-spawned indirection. The dev-test people test the engine without these tricks on the front end; their clients add all kinds of impediments to testing the apps that are built using the engine. Maybe the solution is bureacratic instead of technical. #:) Thanks for the tips. --Kurt -- ---------------------------------------------------------------------- Merlot Research Group, Inc http://www.merlot.com kls[at]merlot.com GPG key 82505A74 Jabber: MerlotQA _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
