When you say, "...the "rescue => e" part of page_set_to_check() doesn't run like I would expect it to..", what exactly do you mean. Am I correct in assuming that the `$something_went_wrong` variable is used inside of the `write_status` method?
If so, is the incorrect behavior coming from what the `write_status` method produces? To validate that your exception is correctly behing handled, put some simple action that will indicate the rescue operation is happening, like: begin page_set rescue => e puts 'inside the rescue now' $something_went_wrong = 'Yes' end write_status end Now if you see `inside the rescue` outputted with an incorrect URL, you'll know you are getting inside the rescue block, and the assignment of `$something_went_wrong` is a syntantically correct statement, so that's not the problem and it should equal `Yes`. The only thing left to check is what's inside the `write_status` function. It could be the case that this function is not behaving correctly in both states, 1) an exception was not thrown, 2) an exception was thrown. If this function relies on `$something_went_wrong` and it is not present, a(n) [silent] error may be occuring. Check out this function or post it's guts to the forums, along with your console output on execution for further assistance if this is not enough to debug your problem. Hope this helps, Nathan Christie --------------------------------------------------------------------- Posted via Jive Forums http://forums.openqa.org/thread.jspa?threadID=6079&messageID=17065#17065 _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
