search

convio / watirmark-example

example project using watirmark framework
1 stars 1 forks source link

Gemfile.lock on private watir branch #1

Open abaird opened 12 years ago

abaird commented 12 years ago

Eric - the lockfile is checked in at 2.0.4.1 which is probably not available in other ppl's repos. 'bundle update' fixes this but I don't know if there is anything in 2.0.4.1 that we are depending on?

abaird commented 12 years ago

Of course, doing an update gets you Watir 2.0.4 which gives you this error when you run with it:

NoMethodError: undefined method nextsibling' for #<Watir::Image:0x3522db0> C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/watir-2.0.4/lib/watir/element.rb:447:inmethod_missing' C:/Users/Alan/RubymineProjects/watirmark-example/lib/salesforce/site/search.rb:89:in look_in_recent_items' C:/Users/Alan/RubymineProjects/watirmark-example/lib/salesforce/site/search.rb:21:insearch' C:/Users/Alan/RubymineProjects/watirmark-example/lib/salesforce/components/lead/lead_view.rb:38:in exists?' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/watirmark-1.2.6/lib/watirmark/webpage/webpage.rb:163:incall_view_method' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/watirmark-1.2.6/lib/watirmark/webpage/webpage.rb:107:in get' C:/Users/Alan/RubymineProjects/watirmark-example/lib/salesforce/spec/test_lead_spec.rb:18:inblock (2 levels) in <top (required)>' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/example.rb:80:in instance_eval' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/example.rb:80:inblock in run' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/example.rb:173:in with_around_hooks' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/example.rb:77:inrun' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/example_group.rb:355:in block in run_examples' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/example_group.rb:351:inmap' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/example_group.rb:351:in run_examples' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/example_group.rb:337:inrun' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/command_line.rb:28:in block (2 levels) in run' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/command_line.rb:28:inmap' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/command_line.rb:28:in block in run' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/reporter.rb:34:inreport' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/command_line.rb:25:in run' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/runner.rb:69:inrun' C:/Ruby193p125/lib/ruby/gems/1.9.1/gems/rspec-core-2.9.0/lib/rspec/core/runner.rb:10:in `block in autorun'

eslater commented 12 years ago

Yea i saw the same error running on that version of watir. 2.0.4.1 seems to fix it and is publicly accessible here and on our gemserver (which is now publicly accessible).

I will remove the lock.

thx