Last modified: 2014-10-19 17:44:07 UTC
My setup: Trisquel GNU/Linux 6.01, Abrowser (fake Firefox) version 28, running GNU bash as my shell, Ruby 2.1.1, rubygems 2.2. t3h logs: marktraceur@midvalley-the-hornfreak:~/projects/wikimedia/mediawiki/core/extensions/MultimediaViewer/tests/browser$ bundle exec cucumber features/basic_mmv_navigation.feature @en.wikipedia.beta.wmflabs.org Feature: Basic Multimedia Viewer navigation Scenario: Multimedia Viewer (MMV) # features/basic_mmv_navigation.feature:4 process still alive after 90 seconds (ChildProcess::TimeoutError) /usr/local/lib/ruby/gems/2.1.0/gems/childprocess-0.5.2/lib/childprocess/abstract_process.rb:152:in `poll_for_exit' /usr/local/lib/ruby/gems/2.1.0/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/firefox/binary.rb:47:in `wait' /usr/local/lib/ruby/gems/2.1.0/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/firefox/launcher.rb:71:in `start_silent_and_wait' /usr/local/lib/ruby/gems/2.1.0/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/firefox/launcher.rb:35:in `block in launch' /usr/local/lib/ruby/gems/2.1.0/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/firefox/socket_lock.rb:20:in `locked' /usr/local/lib/ruby/gems/2.1.0/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/firefox/launcher.rb:32:in `launch' /usr/local/lib/ruby/gems/2.1.0/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/firefox/bridge.rb:24:in `initialize' /usr/local/lib/ruby/gems/2.1.0/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/common/driver.rb:31:in `new' /usr/local/lib/ruby/gems/2.1.0/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver/common/driver.rb:31:in `for' /usr/local/lib/ruby/gems/2.1.0/gems/selenium-webdriver-2.41.0/lib/selenium/webdriver.rb:67:in `for' /usr/local/lib/ruby/gems/2.1.0/gems/watir-webdriver-0.6.8/lib/watir-webdriver/browser.rb:46:in `initialize' /usr/local/lib/ruby/gems/2.1.0/gems/mediawiki_selenium-0.2.16/lib/mediawiki_selenium/support/env.rb:70:in `new' /usr/local/lib/ruby/gems/2.1.0/gems/mediawiki_selenium-0.2.16/lib/mediawiki_selenium/support/env.rb:70:in `local_browser' /usr/local/lib/ruby/gems/2.1.0/gems/mediawiki_selenium-0.2.16/lib/mediawiki_selenium/support/env.rb:26:in `browser' /usr/local/lib/ruby/gems/2.1.0/gems/mediawiki_selenium-0.2.16/lib/mediawiki_selenium/support/hooks.rb:29:in `Before' Given I am at a wiki article with at least two embedded pictures # features/step_definitions/basic_mmv_navigation_steps.rb:1 When I click on the first image in the article # features/step_definitions/basic_mmv_navigation_steps.rb:6 Then the image metadata and the image itself should be there # features/step_definitions/basic_mmv_navigation_steps.rb:55 When I click the next arrow # features/step_definitions/basic_mmv_navigation_steps.rb:22 Then the image and metadata of the next image should appear # features/step_definitions/basic_mmv_navigation_steps.rb:47 When I click the previous arrow # features/step_definitions/basic_mmv_navigation_steps.rb:26 Then the image and metadata of the previous image should appear # features/step_definitions/basic_mmv_navigation_steps.rb:63 When I close MMV # features/step_definitions/basic_mmv_navigation_steps.rb:30 Then I should be navigated back to the original wiki article # features/step_definitions/basic_mmv_navigation_steps.rb:40 Then the wiki article should be scrolled to the same position as before opening MMV # features/step_definitions/basic_mmv_navigation_steps.rb:71 When I click on the first image in the article # features/step_definitions/basic_mmv_navigation_steps.rb:6 And I press the browser back button # features/step_definitions/basic_mmv_navigation_steps.rb:34 Then I should be navigated back to the original wiki article # features/step_definitions/basic_mmv_navigation_steps.rb:40 Then the wiki article should be scrolled to the same position as before opening MMV # features/step_definitions/basic_mmv_navigation_steps.rb:71 undefined method `close' for nil:NilClass (NoMethodError) /usr/local/lib/ruby/gems/2.1.0/gems/mediawiki_selenium-0.2.16/lib/mediawiki_selenium/support/hooks.rb:50:in `After' Failing Scenarios: cucumber features/basic_mmv_navigation.feature:4 # Scenario: Multimedia Viewer (MMV) 1 scenario (1 failed) 14 steps (14 skipped) 1m30.196s
Chris says it's notable that I see a browser for a moment after I hit Ctrl-C to interrupt the tests. 2014-04-22 - 10:09:52 <chrismcmahon> marktraceur: so if you actually do see a browser for a moment after ctrl-c, then something is blocking the step that creates the browser. that shouldn't be possible, but there it is.
for Mark, this step in hooks.rb does not start a browser properly: @browser = browser(test_name(scenario))
This from David Burns (https://github.com/AutomatedTester) in the #selenium channel on IRC: (02:17:50 PM) chrismcmahon: AutomatedTester: ever dealt with Abrowser and webdriver? http://trisquel.info/en/wiki/abrowser-help (or know anyone who has?) (02:18:15 PM) lukeis: heh, why would mozillians use that ;) (02:18:33 PM) AutomatedTester: chrismcmahon: never used it (02:19:18 PM) AutomatedTester: chrismcmahon: why whats the issue? (02:19:29 PM) jimevans: speaking of firefox forks/derivatives i had someone ask me about using the tor browser with webdriver the other day. (02:20:16 PM) chrismcmahon: AutomatedTester: I have a colleague using it. our bog-standard Ruby selenium/watir-webdriver stack does not seem to start the browser (02:20:20 PM) ***lukeis wonders if konqueror will make a resurgence ;) (02:20:31 PM) AutomatedTester: chrismcmahon: what OS? (02:20:45 PM) AutomatedTester: oh wait... silly question (02:21:07 PM) AutomatedTester: chrismcmahon: are they passing in the path to the binary? (02:21:08 PM) chrismcmahon: AutomatedTester: yeah. Trisquel GNU/Linux (02:22:54 PM) chrismcmahon: AutomatedTester: yeah. the weird part is that after a 90-second timeout the browser appears briefly and quits https://bugzilla.wikimedia.org/show_bug.cgi?id=64249 (02:24:39 PM) AutomatedTester: chrismcmahon: very bizarre (02:24:48 PM) chrismcmahon: AutomatedTester: no big deal, this is a crazy corner case, but I like the guy that reported that bug, it'd be nice if webdriver dtrt for him (02:25:23 PM) AutomatedTester: chrismcmahon: its hard to know how abrowser has bastardised Firefox (02:25:51 PM) AutomatedTester: my gut suggests that they have changed something in XPCOM which webdriver uses
