Thanks Charley. I started digging into the ie.goto section a little deeper and was able to figure out what was happening. The script itself is sort of a "quick fix" for an extra QA feature, as sort of a bonus validation. For this reason, I parse the XML like you would read a text file, with a loop that goes line by line looking for anything that's similar to our main web address, yanking the XML tags and throwing it into an array for IE to view. This works fine as long as the XML is in a heirarchical multi-line format. The problem this time, is that the third party that supplied the XML sitemap, removed all of the normal line breaks. This is perfect fine for XML, but an odd and unexpected change for me. My script was still yanking the XML tags one the single line it found, but then it was trying to pump that 90,000 character URL into IE and goto! goto! goto!! Just FYI, IE doesn't like 90,000 character URLs. So, this shows that we've outgrown the current script and need something more robust (probably proper parsing through REXML), and that when you least expect it, consultants will throw a few landmines under your scooter. Thanks again for the direction-- Adam
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Charley Baker Sent: Thursday, May 31, 2007 2:44 PM To: [email protected] Subject: Re: [Wtr-general] Script failing today, but worked yesterday? No idea what's happening without the code, or some reference point. Please post some snippet of code at least, only thing I can tell from this is that there's some problem when you're calling ie.goto. If you haven't changed anything then perhaps the network is wonky or the developers changed something? -Charley On 5/31/07, Adam Reed <[EMAIL PROTECTED]> wrote: This happens from time to time, but never lasted long enough for me to post a topic about it. I have a script that formats an XML file for easier parsing, and then visits each URL listed in this file and ensures that the page is not dead. This scipt has remained unchanged for around two weeks, and has completed successfully each time it has run. Today, I come into the office and attempt to run it, and am receiving an error about 5 seconds after the script is launched (below). I have not had any new Windows or IE updates, nor have I upgraded Watir or Ruby. I also have a compiled .exe version of this script from ruby2exe that obviously cannot be any different than it was yesterday, and it fails with the same errors. I am running IE7 on Windows XP Pro, Watir 1.5.1.1192 (upgraded today from 1145 to troubleshoot -- error occurs with both), and Ruby 1.8.6-25 . I don't believe the code I'm using matters, as the errors I'm getting appear to come from watir itself, but I will post the code if you think it would help. Any ideas? Thanks, Adam Reed 1) Error: test_01_verify_urls(TC_CORE_Suite): WIN32OLERuntimeError: navigate OLE error code:80004005 in <Unknown> <No Description> HRESULT error code:0x80020009 Exception occurred. c:/ruby/lib/ruby/gems/1.8/gems/watir-1.5.1.1145/./watir.rb:1699:in `method_m issing' c:/ruby/lib/ruby/gems/1.8/gems/watir-1.5.1.1145/./watir.rb:1699:in `goto' C:/Documents and Settings/areed/Desktop/automated tests/cort/verify_core_sit emap.rb:24:in `verify' C:/Documents and Settings/areed/Desktop/automated tests/cort/verify_core_sit emap.rb:58:in `test_01_verify_urls' C:/Documents and Settings/areed/Desktop/automated tests/cort/verify_core_sit emap.rb:57:in `each' C:/Documents and Settings/areed/Desktop/automated tests/cort/verify_core_sit emap.rb:57:in `test_01_verify_urls' 1 tests, 0 assertions, 0 failures, 1 errors -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] ] On Behalf Of Chris McMahon Sent: Thursday, May 31, 2007 10:30 AM To: [email protected] Subject: Re: [Wtr-general] A query on Watir - Will watir/firewatir work onLinux? > 2. Is Firewatir completely operational like Watir? (though, I could > see that firewatir is being used currently, I just wants a > confirmation from the appropriate persons) In a sense. Think of it like this: Watir is a set of instructions in Ruby for manipulating Windows OLE and COM interfaces. FireWatir removes the OLE/COM stuff and replaces it with the jssh (javascript shell) Firefox extension. SafariWatir removes the OLE/COM stuff and replaces it with Applescript. In practice, this means that some methods available on one platform won't be available on another platform. Also, since these are all separate projects started at different times and growing at different rates, some features that might be shared, won't be shared. For instance, Watir has a built-in page-load timer, but FireWatir does not. These feature-mismatches are something that Bret, Angrez, and others would like to improve. If you were to use Watir and FireWatir in a serious manner and report discrepancies between them here and on OpenQA/Rubyforge, that would be a big incentive to make the projects share more code and more features. _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
