jakzal / behatnoextension Goto Github PK

Looks like the extension does not comply with the way Behat handles the configuration file and its "variables".

default:
    Zalas\Behat\NoExtension:
      imports:
        - %paths.base%/features/behat/bootstrap/config/services.yml

Throws:

[InvalidArgumentException]
  The file "%paths.base%/features/behat/bootstrap/config/services.yml" does not exist

Shouldn't the %paths.base% be evaluated by the extension, just like Behat does?

I've noticed that services could be loaded only from .yml files but to me it should be possibile to give also .xml format.
Maybe we can let the user decide with this policy: default .yml (will not BC) otherwise specify .xml or we can try find both (but I would prefer a more explicit one).

What do you think?

By following the brief documentation in the README.md it is not clear whether and how it is possible to inject components into a context constructor (by the look of the *.feature files it seems it is possible though).

• How can someone inject an interface in a context which is mapped against a concrete implementation?
• If an interface to be injected in a context has collaborators, how should those be specified?

Please note the use of any Symfony-related component is not assumed here. I'm talking plain POPOs needed to ensure the test suite's codebase is well structured and for its components to be reusable.

Thanks!