The syntax behatch:* for class names is actually also defining
context classes. The BehatchExtension registers a resolver turning
this notation into the actual class names used in Behatch (you can
also use the real class names).
This example also shows how to pass some constructor arguments to
the contexts (which is not used in the case of the MinkContext or in
the example you saw in the doc).
for a given suite, you can configure 3 things (known in core.
extensions can add more settings):
- paths: the paths to the features included in it
- filters: the filters applied on scenarios to restrict them
- contexts: the context classes being used.
the example found in the doc shows the 3 of them. The Behatch sample
only configures contexts, expecting others to rely on the default
values.
--
Christophe | Stof