Behat integration about fastest

[liuggio]

fixed in #12

[liuggio]

Looks great to me 👍

You think that creating a "behat-fastest-driver" would provide some benefits?

What about the output, the adding value of BDD is the documentation did you thought also about this?

The cookie is a good hack but some tests may fails if they do some assertion on the cookies, but I think we could think about it later like a minor issue...

We are on the right way :)

[diegosainz]

Great :) - lets continue to assess common ground on the expected integration...

Behat version I forgot to mention that am implementing this on behat 2.5, with the Symfony2 extension and using Mink with webdriver driver.

A downside of this approach is that the minimum "runnable" unit will be a file containing scenarios, and there could be files with many scenearios and other files with just one, so the load won't be always evenly distributed among the fastest processes.

*About the behat-fastest-driver, what do you mean? - something like behat passing on the tests within behat to *fastest?

About the BDD documentation - I am looking at this implementation from the perspective of running behat scenarios in parallel mainly to accelerate continuous integration. The BDD process should remain the same - just execute your scenarios without fastest or wait for the output of fastest that will provide the details of the failed scenarios. Or what aspect of documentation do you mean?

About the cookie hack I have been thinking about it - we can unset that cookie $_COOKIE after reading it to avoid any side effects, or maybe use a X-FASTEST custom HTTP header. We would have to think how to inject the cookie or header to each page that is called by the Mink driver, to ensure that every request made by the browser to the server has the correct header/cookie in order for Symfony to connect to the correct database. Right now I am using a Behat SubContext to inject the cookie at the same point the authentication is made (in my case that step also needs to create an authenticated cookie on the client side and inject it to the browser). I don't quite like the complexity of this part and I have been thinking on how to make the Symfony/Behat/Mink integration easier - any ideas?

[diegosainz]

About the downside - no longer true - all I had to do is to get recursively the scenarios and their file and line number, that gives an line per scenario as output that can be ran in parallel by fastest/behat :

/somepath/Features/featureOne.feature:10
/somepath/Features/featureOne.feature:20
/somepath/Features/featureTwo.feature:10
/somepath/Features/featureTwo.feature:20

So we may have, maybe --list-features and --list-scenarios options to allow the user to select the level of output desired: at feature-level or scenario-level.

[liuggio]

this sounds lovely and if you keep it simple the result will be awesome,
I can't wait the implementation :)