neos / behat
Behat support package for Neos Flow
Fund package maintenance!
shop.neos.io/neosfunding
Installs: 595 240
Dependents: 20
Suggesters: 1
Security: 0
Stars: 4
Watchers: 5
Forks: 13
Open Issues: 2
Type:neos-package
Requires
- php: ^8.2
- behat/behat: ^3.10
- neos/flow: ^9.0
Replaces
- flowpack/behat: 9.0.0-beta11
- 9.0.x-dev
- 9.0.0-beta11
- 9.0.0-beta10
- 9.0.0-beta2
- 9.0.0-beta1
- 8.4.x-dev
- 8.3.x-dev
- 8.3.0
- 8.2.x-dev
- 8.2.0
- 8.1.x-dev
- 8.1.0
- 8.0.x-dev
- 8.0.0
- 7.3.x-dev
- 7.3.0
- 7.2.x-dev
- 7.2.0
- 7.1.x-dev
- 7.1.0
- 7.0.x-dev
- 7.0.0
- 6.1.x-dev
- 6.1.0
- 6.0.x-dev
- 6.0.0
- 5.2.x-dev
- 5.2.0
- 5.1.x-dev
- 5.1.0
- 5.0.x-dev
- 5.0.1
- 5.0.0
- 4.1.x-dev
- 4.1.1
- 4.1.0
- 4.0.x-dev
- 4.0.0
- 3.0.x-dev
- 3.0.1
- 3.0.0
- 2.4.2
- 2.4.1
- 2.4.0
- 2.3.x-dev
- dev-bugfix/reset-transaction-level
- dev-main
This package is auto-updated.
Last update: 2024-10-24 09:50:39 UTC
README
For running the Behat tests you will need some additional context.
- The context
Testing/Behat
is used inside the Behat feature context to boot flow.
Resetting the database after each scenario.
By using the FlowEntitiesTrait
and tagging the feature with @flowEntities
, the doctrine tables will be dropped.
Make sure to create a new database for the Behat tests as otherwise your data will be lost.
Example configuration
Configuration/Testing/Behat/Settings.yaml
Neos: Flow: persistence: backendOptions: dbname: 'neos_testing_behat' driver: pdo_mysql user: '' password: ''
Migration from neos/behat
< 9.0
Previously when including the FlowContextTrait
, and tagging the feature with @fixture
, it would clear the doctrine tables after each tests.
The new FlowBootstrapTrait
doesn't handle this anymore, but one needs to use the FlowEntitiesTrait
and tag the feature with @flowEntities
Previously we advised to install behat into a separate folder via behat:setup
, but there is currently no need for this complexity.
Now we advise to simply install behat inside the same composer distribution.