search

arknoll / ansible-role-selenium

Ansible Role Selenium
https://galaxy.ansible.com/list#/roles/4340
Other
20 stars 51 forks source link

Chromedriver not working with installed Selenium version #29

Open geerlingguy opened 7 years ago

geerlingguy commented 7 years ago

See: https://github.com/geerlingguy/drupal-vm/issues/1152

Feature: Home page
  In order to verify that the home page is working
  As a user
  I should be able to load the homepage
  With and without Javascript

  @javascript
  Scenario: Load a page with Javascript                   # features/Home Page.feature:8
Starting ChromeDriver 2.27.440175 (9bc1d90b8bfa4dd181fbbf769a5eb5e575574320) on port 27769
Only local connections are allowed.
    Given I am on "/"                                     # Drupal\DrupalExtension\Context\MinkContext::visit()
      Could not open connection: unknown error: Chrome failed to start: exited abnormally
        (Driver info: chromedriver=2.27.440175 (9bc1d90b8bfa4dd181fbbf769a5eb5e575574320),platform=Linux 3.13.0-32-generic x86_64) (WARNING: The server did not provide any stacktrace information)
      Command duration or timeout: 60.28 seconds
      Build info: version: '2.53.1', revision: 'a36b8b1', time: '2016-06-30 17:37:03'
      System info: host: 'local', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-32-generic', java.version: '1.7.0_121'
      Driver info: org.openqa.selenium.chrome.ChromeDriver (Behat\Mink\Exception\DriverException)

It seems there may be two issues here:

  1. The selenium_version needs to be bumped to 3.0.1
  2. The Download Selenium task should have a notify: restart selenium added, so that selenium is restarted if a new version is downloaded...

But I'm still debugging in that other issue to see if this is the actual problem, or just a symptom.

geerlingguy commented 7 years ago

Interestingly, if I change the selenium_version in my Drupal VM config.yml, it looks like the new version is downloaded... but it isn't used, because the next time I ran tests, it was showing:

Build info: version: '2.53.1', revision: 'a36b8b1', time: '2016-06-30 17:37:03'

:/

geerlingguy commented 7 years ago

I found that that was just because BLT used it's own version of selenium-standalone... so we're okay in terms of the PR I posted.