[wtr-general] Re: Browser window close and Javascript popup problem on Watir 1.6.5/Ruby 1.8.6-26
Brett/Charley, I am very sorry for not getting back to you any earlier on this (JMeter performance test priorities at the moment for me too). I've tried this again on watir 1.6.2 - seems like an old bad habit of mine was causing some of the problems in my use of watir 1.6.2, notably the include Watir thing. In my experiments under watir 1.6.2 the issue I reported does NOT occur. So if I do the following from irb (or probably our framework that is built on top of watir for that matter): 1. Attach to the window; ie=Watir::IE.attach(:title,/Blah blah/) 2. Change properties of the application in the window attached to thus dirtying the window. 3. Closing the window; ie.close 4. When I do this, the Javascript popup appears but ie.close COMPLETES (irb does not hang) so that I can subsequently programmatically OK/Cancel the popup. If I do steps 1-3 under watir 1.6.5 then the Javascript popup appears but ie.close BLOCKS (irb hangs, control-C or OK on the Javascript popup unblocks it is required to cause ie.close to complete). So something appears to be some difference change in behaviour (to ie.close???) between watir 1.6.2 and watir 1.6.5. Since these experiments were carried out under IE 8 and Windows 7 in both cases I believe that I can rule these factors out. Hopefully this is of use to you in tracking this possible issue down. Regards, Derek Wong. On Dec 5, 12:23 pm, b...@pettichord.com bpettich...@gmail.com wrote: Can you post the complete stacktrace? Bret On Dec 3, 7:50 pm, DerekW derek.wong...@gmail.com wrote: Just a little update, as yet I've been unable to get Watir 1.6.2 going. Not too sure if it's related to WTR-409 issue that was raised. When I install watir 1.6.2 it seems to want safariwatir (0.3.7) and then when I try doing something from irb it says: MissingSourceFile: no such file to load -- appscript I've tried clean installing Ruby and still no joy. I get the following when I do a gem dependency watir: C:\Users\derekw\Downloads\TestTools\Ruby\rubygems-1.3.5gem dependency watir Gem watir-1.6.2 win32-process (= 0.5.5, runtime) windows-pr (= 0.6.6, runtime) activesupport (= 0, runtime) commonwatir (= 1.6.2, runtime) firewatir (= 0, runtime) Regards, Derek W. On Dec 4, 4:51 am, Charley Baker charley.ba...@gmail.com wrote: Watir 1.6.2 supports attach. Firewatir didn't in 1.6.2, it does in 1.6.5. Charley Baker Lead Developer, Watir,http://watir.com On Wed, Dec 2, 2009 at 4:33 PM, DerekW derek.wong...@gmail.com wrote: Hi Bret, I thought that Watir 1.6.2 did not support attach(). I remembered reading in the 1.6.2 release notes that attach wasn't supported so this was the reason I held back on 1.5.6 before moving to 1.6.5. Please correct me if I've misinterpreted something here. Thanks. Derek W. On Dec 3, 6:44 am, b...@pettichord.com bpettich...@gmail.com wrote: One thing you might try, in order to track things down, would be to try running your tests with with Watir 1.6.2. If you do this, you should manually install firewatir 1.6.2 also (gem install firewatir -v 1.6.2). And then uninstall any newer watir gems (if any). Bret On Dec 1, 2:41 pm, DerekW derek.wong...@gmail.com wrote: To further clarify: My colleague's machine: Windows XP, Ruby 1.8.2-14, Watir 1.5.6 and IE 8 - test works. The other test machines: Windows 7 Enterprise, Ruby 1.8.6-26, Watir 1.6.5 and IE 8 - test does not work. So, potentially it could be Windows or Watir issue. Unfortuantely, I haven't tried the old Ruby/Watir against Windows 7 configuration to eliminate the OS yet. Derek W. On Dec 1, 6:30 pm, DerekW derek.wong...@gmail.com wrote: Hi, here's a scenario that seems to work in Watir 1.5.6 but seems to exhibit problems under 1.6.5: Our web application opens the main browser window and subsequently two other browser windows, the third browser window attaches an event handler that intercepts the close window (X) button. If the third window's browser state is dirty and the user clicks close window (rather than the OK and Cancel) buttons on the browser page it raises a Javascript popup asking whether the user wants to navigate away from this browser window. When we ran our automated tests using Watir 1.5.6 this test was able to navigate past the popup raised when the user attempted to click the close button. On Watir 1.6.5 we've noticed that we hang when the popup is hit. Anyone know of a nice way of handling this or whether what I observe is a bug or change in the behaviour of Watir 1.6.5 - my colleague's machine still has Ruby 1.8.2-14, Watir 1.5.6 and IE 8 and the test case works fine. Thanks for any help.
[wtr-general] Re: Browser window close and Javascript popup problem on Watir 1.6.5/Ruby 1.8.6-26
One thing you might try, in order to track things down, would be to try running your tests with with Watir 1.6.2. If you do this, you should manually install firewatir 1.6.2 also (gem install firewatir -v 1.6.2). And then uninstall any newer watir gems (if any). Bret On Dec 1, 2:41 pm, DerekW derek.wong...@gmail.com wrote: To further clarify: My colleague's machine: Windows XP, Ruby 1.8.2-14, Watir 1.5.6 and IE 8 - test works. The other test machines: Windows 7 Enterprise, Ruby 1.8.6-26, Watir 1.6.5 and IE 8 - test does not work. So, potentially it could be Windows or Watir issue. Unfortuantely, I haven't tried the old Ruby/Watir against Windows 7 configuration to eliminate the OS yet. Derek W. On Dec 1, 6:30 pm, DerekW derek.wong...@gmail.com wrote: Hi, here's a scenario that seems to work in Watir 1.5.6 but seems to exhibit problems under 1.6.5: Our web application opens the main browser window and subsequently two other browser windows, the third browser window attaches an event handler that intercepts the close window (X) button. If the third window's browser state is dirty and the user clicks close window (rather than the OK and Cancel) buttons on the browser page it raises a Javascript popup asking whether the user wants to navigate away from this browser window. When we ran our automated tests using Watir 1.5.6 this test was able to navigate past the popup raised when the user attempted to click the close button. On Watir 1.6.5 we've noticed that we hang when the popup is hit. Anyone know of a nice way of handling this or whether what I observe is a bug or change in the behaviour of Watir 1.6.5 - my colleague's machine still has Ruby 1.8.2-14, Watir 1.5.6 and IE 8 and the test case works fine. Thanks for any help. Derek W. PS - Having said this my experience of Watir 1.6.5 has been pretty positive so far. -- You received this message because you are subscribed to the Google Groups Watir General group. To post to this group, send email to watir-general@googlegroups.com Before posting, please read the following guidelines: http://wiki.openqa.org/display/WTR/Support To unsubscribe from this group, send email to watir-general-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/watir-general
[wtr-general] Re: Browser window close and Javascript popup problem on Watir 1.6.5/Ruby 1.8.6-26
Hi Bret, I thought that Watir 1.6.2 did not support attach(). I remembered reading in the 1.6.2 release notes that attach wasn't supported so this was the reason I held back on 1.5.6 before moving to 1.6.5. Please correct me if I've misinterpreted something here. Thanks. Derek W. On Dec 3, 6:44 am, b...@pettichord.com bpettich...@gmail.com wrote: One thing you might try, in order to track things down, would be to try running your tests with with Watir 1.6.2. If you do this, you should manually install firewatir 1.6.2 also (gem install firewatir -v 1.6.2). And then uninstall any newer watir gems (if any). Bret On Dec 1, 2:41 pm, DerekW derek.wong...@gmail.com wrote: To further clarify: My colleague's machine: Windows XP, Ruby 1.8.2-14, Watir 1.5.6 and IE 8 - test works. The other test machines: Windows 7 Enterprise, Ruby 1.8.6-26, Watir 1.6.5 and IE 8 - test does not work. So, potentially it could be Windows or Watir issue. Unfortuantely, I haven't tried the old Ruby/Watir against Windows 7 configuration to eliminate the OS yet. Derek W. On Dec 1, 6:30 pm, DerekW derek.wong...@gmail.com wrote: Hi, here's a scenario that seems to work in Watir 1.5.6 but seems to exhibit problems under 1.6.5: Our web application opens the main browser window and subsequently two other browser windows, the third browser window attaches an event handler that intercepts the close window (X) button. If the third window's browser state is dirty and the user clicks close window (rather than the OK and Cancel) buttons on the browser page it raises a Javascript popup asking whether the user wants to navigate away from this browser window. When we ran our automated tests using Watir 1.5.6 this test was able to navigate past the popup raised when the user attempted to click the close button. On Watir 1.6.5 we've noticed that we hang when the popup is hit. Anyone know of a nice way of handling this or whether what I observe is a bug or change in the behaviour of Watir 1.6.5 - my colleague's machine still has Ruby 1.8.2-14, Watir 1.5.6 and IE 8 and the test case works fine. Thanks for any help. Derek W. PS - Having said this my experience of Watir 1.6.5 has been pretty positive so far. -- You received this message because you are subscribed to the Google Groups Watir General group. To post to this group, send email to watir-general@googlegroups.com Before posting, please read the following guidelines: http://wiki.openqa.org/display/WTR/Support To unsubscribe from this group, send email to watir-general-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/watir-general
