veyra/friends-of-behat-mink-extension
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

numbered list

Browse Source
This commit is contained in:
everzet
2012-05-11 11:35:13 +02:00
parent d208119538
commit f0ae430089
1 changed files with 23 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
README.md
View File

@@ -52,31 +52,31 @@ Usage
After installing extension, there would be 5 usage options available for you: After installing extension, there would be 5 usage options available for you:
* Writing features with bundled steps only. In this case, you don't need to create 1. Writing features with bundled steps only. In this case, you don't need to create
`boostrap/` folder or custom `FeatureContext` class - Behat will use default `boostrap/` folder or custom `FeatureContext` class - Behat will use default
`MinkContext` by default. `MinkContext` by default.
* Subcontexting/extending `Behat\MinkExtension\Context\RawMinkContext` in your feature suite. 2. Subcontexting/extending `Behat\MinkExtension\Context\RawMinkContext` in your feature suite.
This will give you ability to use preconfigured `Mink` instance altogether with some This will give you ability to use preconfigured `Mink` instance altogether with some
convenience methods: convenience methods:
- `getSession($name = null)` - `getSession($name = null)`
- `assertSession($name = null)` - `assertSession($name = null)`
`RawMinkContext` doesn't provide any hooks or definitions, so you can inherit from it `RawMinkContext` doesn't provide any hooks or definitions, so you can inherit from it
in as many subcontexts as you want - you'll never get `RedundantStepException`. in as many subcontexts as you want - you'll never get `RedundantStepException`.
* Subcontexting/extending `Behat\MinkExtension\Context\MinkContext` in your feature suite. 3. Subcontexting/extending `Behat\MinkExtension\Context\MinkContext` in your feature suite.
Exactly like previous option, but also provides lot of predefined step definitions out Exactly like previous option, but also provides lot of predefined step definitions out
of the box. As this context provides step definitions and hooks, you can use it **only once** of the box. As this context provides step definitions and hooks, you can use it **only once**
inside your feature context tree. inside your feature context tree.
* If you're on the php 5.4+, you can simply use `Behat\MinkExtension\Context\MinkDictionary` 4. If you're on the php 5.4+, you can simply use `Behat\MinkExtension\Context\MinkDictionary`
trait inside your `FeatureContext` or any of its subcontexts. This trait will provide trait inside your `FeatureContext` or any of its subcontexts. This trait will provide
all the needed methods, hooks and definitions for you to start. You can use this trait **only all the needed methods, hooks and definitions for you to start. You can use this trait **only
once** inside your feature context tree. once** inside your feature context tree.
* Implementing `Behat\MinkExtension\Context\MinkAwareContextInterface` with your context or its 5. Implementing `Behat\MinkExtension\Context\MinkAwareContextInterface` with your context or its
subcontexts. subcontexts.
This will give you more customization options. Also, you can use this mechanism on multiple This will give you more customization options. Also, you can use this mechanism on multiple
contexts avoiding the need to call parent contexts from subcontexts when only thing you need contexts avoiding the need to call parent contexts from subcontexts when only thing you need
is mink instance. is mink instance.
There's common things between last 4 methods. In each of those, target context will implement There's common things between last 4 methods. In each of those, target context will implement
`setMink(Mink $mink)` and `setMinkParameters(array $parameters)` methods. Those methods would `setMink(Mink $mink)` and `setMinkParameters(array $parameters)` methods. Those methods would