|
reproduced with using environement below $ uname -a $ ruby -v $ gem list
activesupport (2.3.8) thanks andy, your suggestion worked ! so 1. replace the win32ole.so file so it matches the default ruby one 2. add the : unless RUBY_PLATFORM == 'i386-cygwin' and the default Watir example works (didn't need the other line update, maybe it will resurface later when i more seriously use watir) watir team : please run tests on cygwin too I have a completely different question which is not directly related with this issue - why are you even using Cygwin with Ruby and Firewatir? Just out of curiousity what's the real life usecase. simple : i am coerced into using windows. but i do like the wealth of the gnu environment, for starters using bash instead of cmd is a real productivity gain. that was for the first point. second point is i am evaluating watir and trying to figure out if it is really a benefit compared to selenium for instance (so far i am not convinced but willing to really investigate the issue). so i need to see the same testing script working on both ie and firefox. following andy comments on http://jira.openqa.org/browse/WTR-453 that was the second point last but not last, i faced plain not-working-firewatir going through the route of the watir installation guide http://watir.com/installation/#win that was the last point. i think having watir actually support cygwin seems really easy honnestly (about 3 lines to update, only 10 caracters for firewatir), so it is worth doing i'd say. You may be interested to know that I tested early versions of Watir on cygwin regularly. There is some code in our unit tests which is there specifically to support the file syntax of cygwin. If this is still a problem, please report it here: https://github.com/watir/watir-classic/issues |
|||||||||||||||||||||||||||||||||||||
Having the same issue. Please patch when you can. Thanks.