Yes, i think the jssh plugin needs to be updated. Anyone want to give it 
a try?

Bret


Daniel wrote:
> I know what my problem is.
>
> I have firefox 3.0.7
>
> On Mar 8, 2:50 pm, Bret Pettichord <[email protected]> wrote:
>   
>> This looks like two different problems.
>>
>> 1. you are having a problem with jssh
>> 2. you are having a problem with the unit tests
>>
>> My answers
>>
>> 1. you need to provide more information
>> 2. as i said before the unit tests won't run from the gem. this does not
>> indicate an install problem.
>>
>> Daniel Korman wrote:
>>     
>>> Im having a problem with the installation. I installed the jssh add on
>>> for firfox, started firefox with the jssh option (/firefox-bin -jssh)
>>> but I still can't telnet to port 9997 and when I try to run the tests
>>> I get
>>>       
>>> bash-3.2# ruby mozilla_all_tests.rb
>>> /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in
>>> `gem_original_require': no such file to load -- unittests/setup/lib
>>> (LoadError)
>>>    from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require'
>>>    from /Library/Ruby/Gems/1.8/gems/firewatir-1.6.2/unittests/setup.rb:15
>>>    from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in
>>> `gem_original_require'
>>>    from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require'
>>>    from mozilla_all_tests.rb:5
>>>       
>>> On Sun, Mar 8, 2009 at 10:13 AM, Bret Pettichord <[email protected]> 
>>> wrote:
>>>       
>>>> yes, there is a way to run the unit tests onmac. is that your problem?
>>>>         
>>>> Daniel wrote:
>>>>         
>>>>> Im having the same problem as jbgene, is there any kind of solution?
>>>>>           
>>>>> On Feb 19, 11:50 am, Bret Pettichord <[email protected]> wrote:
>>>>>           
>>>>>> Thefirewatir/watir unit tests will not run from the gem with
>>>>>> Watir/Firewatir1.6.x on any platform.
>>>>>>             
>>>>>> Bret
>>>>>>             
>>>>>> jbgene wrote:
>>>>>>             
>>>>>>> You are correct. My issue is different but this thread was in the
>>>>>>> vicinity of mine so I posted.
>>>>>>>               
>>>>>>> Here's the detail you requested.
>>>>>>>               
>>>>>>> I'm simply trying to run mozilla_all_tests.rb, per thefirewatir
>>>>>>> instructions.
>>>>>>>               
>>>>>>> When I do, I get this:
>>>>>>>               
>>>>>>> /opt/local/lib/ruby/gems/1.8/gems/firewatir-1.6.2/unittests/setup.rb:
>>>>>>> 15:in `require': no such file to load -- watir (LoadError)
>>>>>>>    from /opt/local/lib/ruby/gems/1.8/gems/firewatir-1.6.2/unittests/
>>>>>>> setup.rb:15
>>>>>>>    from mozilla_all_tests.rb:3:in `require'
>>>>>>>    from mozilla_all_tests.rb:3
>>>>>>>               
>>>>>>> When I try a suggested workaround of adding "require rubygems", I get
>>>>>>> this:
>>>>>>>               
>>>>>>> /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:31:in
>>>>>>> `gem_original_require': no such file to load -- unittests/setup/lib
>>>>>>> (LoadError)
>>>>>>>    from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:
>>>>>>> 31:in `require'
>>>>>>>    from /opt/local/lib/ruby/gems/1.8/gems/firewatir-1.6.2/unittests/
>>>>>>> setup.rb:17
>>>>>>>    from mozilla_all_tests.rb:3:in `require'
>>>>>>>    from mozilla_all_tests.rb:3
>>>>>>>               
>>>>>>> Again, I've tried with the stock OSX Ruby install and the MacPorts
>>>>>>> Ruby install. With the former "require watir" works at the irb command
>>>>>>> line, but fails in script. With the latter, "require watir" fails both
>>>>>>> at the irb command line and in script.
>>>>>>>               
>>>>>>> On Feb 19, 12:49 am, John Kolokotronis <[email protected]> wrote:
>>>>>>>               
>>>>>>>> Bret is correct - Watir does indeed work correctly onMacOS X and
>>>>>>>> you're probably having a different problem than I was. Sorry for
>>>>>>>> forgetting to post back, butFireWatirand SafariWatir are indeed
>>>>>>>> working correctly on Leopard 10.5.6 for me now - for some reason,
>>>>>>>> installingFireWatirfirst and then SafariWatir (instead of the other
>>>>>>>> way around which I originally did), worked fine and the common
>>>>>>>> Watir::Browser.default option is working correctly in setting Safari
>>>>>>>> as the browser to work with.FireWatirhas always worked as expected
>>>>>>>> for me.
>>>>>>>>                 
>>>>>>>> Regards,
>>>>>>>>                 
>>>>>>>> John
>>>>>>>>                 
>>>>>>>> On Feb 19, 5:21 am, Bret Pettichord <[email protected]> wrote:
>>>>>>>>                 
>>>>>>>>> Many of us are running fine on OSX.
>>>>>>>>>                   
>>>>>>>>> If you give us some more information about your problem maybe we can
>>>>>>>>> help you. It seems like you are having a different problem than John.
>>>>>>>>>                   
>>>>>>>>> Bret
>>>>>>>>>                   
>>>>>>>>> jbgene wrote:
>>>>>>>>>                   
>>>>>>>>>> Was the lack of full support for watir on OSX ever resolved. I've
>>>>>>>>>> tried both the built-in Leopard ruby install and the MacPorts ruby
>>>>>>>>>> installs and neither help me avoid this error from the firewater
>>>>>>>>>> unittests:
>>>>>>>>>>                     
>>>>>>>>>> require': no such file to load -- watir (LoadError)
>>>>>>>>>>                     
>>>>>>>>>> On Feb 10, 2:28 am, John Kolokotronis <[email protected]> wrote:
>>>>>>>>>>                     
>>>>>>>>>>> I have to get back to myMaclater today to check, but I definitely
>>>>>>>>>>> can't get Safari set as the default. This actually does give me the
>>>>>>>>>>> same feedback in irb on my system:
>>>>>>>>>>>                       
>>>>>>>>>>>>> Watir::Browser.default = 'safari'
>>>>>>>>>>>>>                           
>>>>>>>>>>> => "safari"
>>>>>>>>>>>                       
>>>>>>>>>>> But then Watir::Browser.new attempts to launch FF anyway. I wonder 
>>>>>>>>>>> if
>>>>>>>>>>> the gem installation order affects anything?
>>>>>>>>>>>                       
>>>>>>>>>>> As I did a rubygems system update first, then SafariWatir, then
>>>>>>>>>>> FireWatirlast (which also installed commonWatir methods - didn't 
>>>>>>>>>>> work
>>>>>>>>>>> at all with only SafariWatir installed) - I might try that later.
>>>>>>>>>>>                       
>>>>>>>>>>> Watir::Safari.new does work though and launches Safari as 
>>>>>>>>>>> expected...
>>>>>>>>>>>                       
>>>>>>>>>>> On Feb 10, 2:19 am, Bret Pettichord <[email protected]> wrote:
>>>>>>>>>>>                       
>>>>>>>>>>>> 1. What you report is a bug. It should work with Safari. It does 
>>>>>>>>>>>> on my
>>>>>>>>>>>> machine.
>>>>>>>>>>>>                         
>>>>>>>>>>>> derrida:~ bret$ irb
>>>>>>>>>>>>  >> require 'watir'
>>>>>>>>>>>> => true
>>>>>>>>>>>>  >> Watir::Browser.default = 'safari'
>>>>>>>>>>>> => "safari"
>>>>>>>>>>>>  >> Watir::Browser.new
>>>>>>>>>>>> => #<Watir::Safari:0x11218e8 
>>>>>>>>>>>> @scripter=#<Watir::AppleScripter:0x111b344
>>>>>>>>>>>> @typing_lag=0.08, @app=app("/Applications/Safari.app"),
>>>>>>>>>>>> @document=app("/Applications/Safari.app").documents[1],
>>>>>>>>>>>> @js=#<Watir::JavaScripter:0x111b31c>>>
>>>>>>>>>>>>                         
>>>>>>>>>>>> 2. If you don't want to useFireWatirat all, you should be able to 
>>>>>>>>>>>> just
>>>>>>>>>>>> install safariwatir and commonwatir (directly).
>>>>>>>>>>>>                         
>>>>>>>>>>>> derrida:~ bret$ gem uninstallfirewatir
>>>>>>>>>>>>                         
>>>>>>>>>>>> Select gem to uninstall:
>>>>>>>>>>>>  1.firewatir-1.2.1
>>>>>>>>>>>>  2.firewatir-1.6.1
>>>>>>>>>>>>  3. All versions
>>>>>>>>>>>>  > 3
>>>>>>>>>>>> Successfully uninstalledfirewatir-1.2.1
>>>>>>>>>>>> Successfully uninstalledfirewatir-1.6.1
>>>>>>>>>>>> derrida:~ bret$ irb
>>>>>>>>>>>>  >> require 'watir'
>>>>>>>>>>>> => true
>>>>>>>>>>>>  >> Watir::Browser.default = 'safari'
>>>>>>>>>>>> => "safari"
>>>>>>>>>>>>  >> Watir::Browser.new
>>>>>>>>>>>> => #<Watir::Safari:0x113a3d4 
>>>>>>>>>>>> @scripter=#<Watir::AppleScripter:0x1133ed0
>>>>>>>>>>>> @app=app("/Applications/Safari.app"),
>>>>>>>>>>>> @document=app("/Applications/Safari.app").documents[1],
>>>>>>>>>>>> @js=#<Watir::JavaScripter:0x1133ea8>, @typing_lag=0.08>>
>>>>>>>>>>>>                         
>>>>>>>>>>>> Bret
>>>>>>>>>>>>                         
>>>>>>>>>>>> John Kolokotronis wrote:
>>>>>>>>>>>>                         
>>>>>>>>>>>>> Thanks for the reply Bret. I hadn't installedFirewatiryet and it
>>>>>>>>>>>>> seems commonwatir is only installed with that, not with 
>>>>>>>>>>>>> Safariwatir.
>>>>>>>>>>>>> However, after installing both, the methods do work, but at least 
>>>>>>>>>>>>> in
>>>>>>>>>>>>> irb, even after setting Watir::Browser.default = "safari',
>>>>>>>>>>>>> Watir::Browser.new continues to launch Firefox?
>>>>>>>>>>>>>                           
>>>>>>>>>>>>> On Feb 9, 8:37 pm, Bret Pettichord <[email protected]> wrote:
>>>>>>>>>>>>>                           
>>>>>>>>>>>>>> John Kolokotronis wrote:
>>>>>>>>>>>>>>                             
>>>>>>>>>>>>>>> The wiki also still mentions thatMacinstallation is done with:
>>>>>>>>>>>>>>>                               
>>>>>>>>>>>>>>> sudo gem update --system
>>>>>>>>>>>>>>> sudo gem installfirewatir
>>>>>>>>>>>>>>> sudo gem install safariwatir
>>>>>>>>>>>>>>>                               
>>>>>>>>>>>>>>> But that doesn't give you common Watir methods, like
>>>>>>>>>>>>>>> Watir::Browser.new - so in that context, how do you use
>>>>>>>>>>>>>>> "Watir::Browser.default = 'safari'"?
>>>>>>>>>>>>>>>                               
>>>>>>>>>>>>>> If you are not getting these methods in this scenario, that is a 
>>>>>>>>>>>>>> bug. Is
>>>>>>>>>>>>>> that really what is happening?
>>>>>>>>>>>>>>                             
> >
>   


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Watir General" group.
To post to this group, send email to [email protected]
Before posting, please read the following guidelines: 
http://wiki.openqa.org/display/WTR/Support
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/watir-general
-~----------~----~----~----~------~----~------~--~---

Reply via email to