Behat 3 Support

[jamescowie]

Behat 3 has now been released from some time and offers enhanced functionality for suites of features and other optimisations. We have also created a stand along library for handling fixture generation and management. However we also need to retain a version of BehatMage that supports Behat 2 as Behat 3 is not backwards compatible. The current beta branch is feature/Behat3

My objectives are:

• Update the extension to support Behat 3
• Update composer.json with pinned versions of PHPSpec, Behat
• Ensure module is covered with Behat features and PHPSpecs
• Remove fixture factory
• Add MageTest manager as dependency in composer
• Remove non essential context steps
• Improve documentation
• Include examples of usage and patterns for testing Magento ( adapter )
• Explore possibility for more Page Objects potentially remove from this extension and have stand alone library / extension.

[ciaranmcnulty]

👍

[danielkmariam]

👍

[jamescowie]

Removed adding Manager as a dependency within the extension. However I will provide more examples showing how the manager can be used within the Feature Contexts.

[mikewhitby]

👍 Out of interest, is there a paticular reason why the composer.json has a version of ~2.4.4 for behat/behat? I ask because it seems like that is forcing behat/mink-extension on to v1.1.4, which does not support adding multiple sessions to allow annotating scenarios in order to run them using sessions. Fairly limited on my behat understanding but it seems this is the case.

[jamescowie]

Hello,

In composer.json I have behat pinned to ~3 and the mink extensions set to use * For mink I should probably look at a major release. The branch to look at for Behat 3 is feature/Behat3 and issues feel free to let me know

[robjstanley]

@jamescowie what happened to MageTest\MagentoExtension\Fixtures? Is the MageTest/Manager now a dependancy in their place?

[aftabnaveed]

feature/Behat3 would not work, instead I used dev-feature/Behat3 instead, is there any difference between both?

[pufferfishareliars]

@jamescowie: Currently it looks like composer.json is pinned to 3.0.15 rather than ~3 on the feature/Behat3 branch. Would be nice to be able to upgrade to Behat v3.1 while still using this package if compatible.