You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks to http://packanalyst.com/class?q=Behat\Mink\Driver\DriverInterface I found the implemetations of our DriverInterface in Packagist packages. Apart from several child classes of our drivers for specific testsuite needs (not always necessary for Mink 1.6 btw), this allowed me to detect 2 different implementations of a capybara-webkit driver, which was initially proposed in minkphp/Mink#221 (but never completed). I requested the status of these drivers, as they are both forcing to use Mink 1.5 currently.
I suggest adding section about third-party drivers in http://mink.behat.org/en/latest/guides/drivers.html once we get answers from the respective maintainers to know whether they want them to be listed (a prerequisite would be to make them compatible with Mink 1.6 and a nice-to-have would be to make them run the Mink 1.6+ driver testsuite):
Well, they can be moved to the minkphp organization only if their current maintainers continue to maintain them actively. I don't want to have yet another driver which will fall into our own workload because other maintainers stop working on them.
Thanks to http://packanalyst.com/class?q=Behat\Mink\Driver\DriverInterface I found the implemetations of our DriverInterface in Packagist packages. Apart from several child classes of our drivers for specific testsuite needs (not always necessary for Mink 1.6 btw), this allowed me to detect 2 different implementations of a capybara-webkit driver, which was initially proposed in minkphp/Mink#221 (but never completed). I requested the status of these drivers, as they are both forcing to use Mink 1.5 currently.
I suggest adding section about third-party drivers in http://mink.behat.org/en/latest/guides/drivers.html once we get answers from the respective maintainers to know whether they want them to be listed (a prerequisite would be to make them compatible with Mink 1.6 and a nice-to-have would be to make them run the Mink 1.6+ driver testsuite):
The text was updated successfully, but these errors were encountered: