The behat.travis.yml file has a profile for Chrome browser testing. behat.template.yml needs to have this too, otherwise scenarios tagged with @chrome will either fail or be skipped when tested locally.

CommentFileSizeAuthor
#2 panopoly-chrome-profile-2294515-1.patch1.24 KBcboyden

Comments

cboyden’s picture

cboyden commented
Issue summary: View changes
cboyden’s picture

cboyden commented
Status: Active » Needs review
StatusFileSize
new panopoly-chrome-profile-2294515-1.patch1.24 KB

Patch attached. Adds Chrome profile to behat.template.yml and a brief explanation to README.

cboyden’s picture

cboyden commented
Issue summary: View changes
dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
commented

So, the reason I didn't include this, was that those tests actually pass for me on Firefox about 90% of the time. It's just that pesky 10% where they go wrong. :-)

However, yeah, we probably should include this! In order to run tests on Chrome, you additionally have to install the ChromeDriver:

http://code.google.com/p/selenium/wiki/ChromeDriver

Could you add something about that to the documentation? Thanks!

cboyden’s picture

cboyden commented

They crash for me every time on FF. And I'm pretty sure I do not have ChromeDriver installed, I just say

browser_name: chrome

in the Behat\MinkExtension\Extension section and all the tests run on Chrome.

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
commented

Interesting!

Well, I needed to install ChromeDriver in order for them to work for me and on Travis-CI - maybe it's a Linux thing? Anyway, ChromeDriver is available for Mac and Windows so I assumed it was necessary there too. But I'll take your word for it!

  • dsnopek committed 1a372c7 on 7.x-1.x 
    Update Panopoly Test for #2294515 by cboyden: Fixed Behat template for...
dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
commented
Status: Needs review » Fixed

Re-rolled for the move to panopoly_test and committed there! Thanks again! :-)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.