Behat suite should be covering the features of the extension

[stof]

Currently, the behat suite is not covering the extension. It is an example project using the extension to cover the example-app. This has several drawbacks:

• it does not allow you to cover error cases of the extension (as you are not asserting the behavior of the extension but using it and so an error would be a CI failure)
• it does not give meaningful errors on failure
• it makes it hard to test different configurations
• it does not allow to use the scenarios as documentation (as scenarios are not describing the usage of the extension but of the example app)

I know where your setup comes from: you copied MinkExtension, which suffers from these flaws (rewriting its suite is at the bottom of my todo-list since years).
You can look at the Symfony2Extension for a suite which would run Behat inside its context instead (scenarios are not very descriptive, as they still rely on an example app rather than describing everything in the feature file, but it still solve some of the cases above)

[ciaranmcnulty]

The problem I had trying to write features was that there isn't really any behaviour to test - it's simple API translation pretty much everywhere.

Any ideas on how to capture the behaviour as scenarios would be appreciated - as you rightly say the Symfony2Extension ones still strongly depend on an example app.