Package Data | |
---|---|
Maintainer Username: | Teoble |
Maintainer Contact: | buzachis.aris@gmail.com (Aris Buzachis) |
Package Create Date: | 2018-11-29 |
Package Last Update: | 2018-11-29 |
Language: | PHP |
License: | MIT |
Last Refreshed: | 2024-11-08 03:11:28 |
Package Statistics | |
---|---|
Total Downloads: | 4,699 |
Monthly Downloads: | 43 |
Daily Downloads: | 3 |
Total Stars: | 3 |
Total Watchers: | 1 |
Total Forks: | 0 |
Total Open Issues: | 1 |
The purpose of the project is to make available the behat-lumen-extension for Lumen higher versions than v5.1, since that in the original project it works on in v5.2.
Thanks for Aris Buzachis for developing suching an helping tool as behat-lumen-extension
As always, we need to pull in some dependencies through Composer.
composer require behat/behat behat/mink behat/mink-extension teoble/behat-lumen-extension --dev
This will give us access to Behat, Mink, and, of course, the Lumen extension.
If you want to use a custom .env file for the Behat tests you will need to modify bootstrap/app.php
like this:
try {
(new Dotenv\Dotenv(__DIR__.'/../', isset($dotEnvFile) ?: '.env'))->load();
} catch (Dotenv\Exception\InvalidPathException $e) {
//
}
Next, within your project root, create a behat.yml
file, and add:
default:
autoload: [ %paths.base%/tests/functional/contexts ]
extensions:
Arisro\Behat\ServiceContainer\LumenExtension:
# env_file: .env.behat
Behat\MinkExtension:
default_session: lumen
lumen: ~
suites:
default:
paths: [ %paths.base%/tests/functional/features ]
filters:
contexts:
- FeatureContext
Optinally, you can specify a different .env file for your functional tests (with a test DB for example).
You have a very small example here https://github.com/arisro/behat-lumen-example.
Note: if you want to leverage some of the Mink helpers in your FeatureContext
file, then be sure to extend Behat\MinkExtension\Context\MinkContext
.