Adding @javascript throws different errors depending on browser profile

[richardtape]

Hi!

I absolutely love this, and I'm in the process of integrating it into a testing suite we're building. Without any javascript requirements, this works flawlessly. Thanks so much.

However, when I add @javascript to a feature and then run something like

docker-compose run behat --profile=phantomjs I get

[InvalidArgumentException]              
  Session "phantomjs" is not registered. 

If I try docker-compose run behat --profile=chrome then I get

 Could not open connection: Error forwarding the new session Empty pool of VM for setup Capabilities [{deviceType=ANY, selenium-version=2.31.0, browser=chrome, browserVersion=9, name=Behat Test, browserName=chrome, deviceOrientation=portrait, ignoreZoomSetting=false, version=ANY, platform=ANY, max-duration=300}]

An example feature is

@ctltsearch
Feature: Test that search returns valid results

@javascript
Scenario: Search for 'hello' returns a post
Given I am on "http://53.spaces.dev/"
When I fill ".search-field" with "hello"
Then I hit return
Then I should be on "http://53.spaces.dev/?s=hello"
And I should see "Search Results for: hello"
And I should see "Hello world!"

I'm almost certainly doing something stupid, so if you could point me in the right direction I would really appreciate it. Again, thanks so much!

[phibsholo]

Hi guys!!

To me happen the same, I don't know what is the good practice to use tests with javascript.

Do you have some suggestion?

[phibsholo]

I found the solution, because on documentation in any place says that we need to execute:
docker-compose up -d

But after read an owner article I release that this command have to be executed and, after do this, it works ;)

But this solution only works for chrome and firefox, phantomjs still showing:
Session "phantomjs" is not registered.

[phibsholo]

Error appears again :(