Improve readme

[uuf6429]

Fixes #4.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.76%. Comparing base (ea2ee82) to head (4b888e5).

Additional details and impacted files

@@            Coverage Diff            @@
##               main      #19   +/-   ##
=========================================
  Coverage     81.76%   81.76%           
  Complexity      191      191           
=========================================
  Files             1        1           
  Lines           488      488           
=========================================
  Hits            399      399           
  Misses           89       89           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[stof]

We could copy it from the Testing section (maybe with a sentence mentioning that you could also run the browser-specific driver directly instead of Selenium depending on your use case)

[aik099]

@uuf6429 , could you please remind me where the sample .behat.yml was supposed to live?

[uuf6429]

@uuf6429 , could you please remind me where the sample .behat.yml was supposed to live?

@aik099 Didn't we say we're not providing a sample behat config? Otherwise I don't know what's this about..it's been quite a while now.

[aik099]

@uuf6429 , could you please remind me where the sample .behat.yml was supposed to live?

@aik099 Didn't we say we're not providing a sample behat config? Otherwise I don't know what's this about..it's been quite a while now.

Would that sample configuration file be located in MinkExtension repo?

[uuf6429]

Would that sample configuration file be located in MinkExtension repo?

@aik099 it feels more like it should be in the documentation somewhere. If we did put it in the repo, it would probably be lost (export-ignore'd), so devs wouldn't find it anyway.

[stof]

MinkExtension has a doc folder, where it documents all drivers it supports with its factories. That's where things should go.
The Mink driver themselves should not care about the Behat extension that is using them.

[uuf6429]

MinkExtension has a doc folder, where it documents all drivers it supports with its factories. That's where things should go. The Mink driver themselves should not care about the Behat extension that is using them.

It's the first time I see that - totally wasn't aware of it. The last change there is 7 years ago, by the way (that said it looks very useful, just maybe not very visible).

[aik099]

Would posting a link on https://github.com/FriendsOfBehat/MinkExtension/blob/master/doc/index.rst page, that will explain how to connect this driver specifically to Behat hurt?

// cc @stof .

[uuf6429]

I think it's a good idea.