friends-of-behat/suite-settings-extension
Behat extension that lets you define default suite settings once and have every suite inherit them. Configure default paths and contexts in behat.yml so new suites pick them up automatically, avoiding repetition.
|
Package
|
Score
|
Description
|
Stars
|
Likes
|
Forks
|
Downloads
|
Issues
|
Score
|
Opportunity
|
License
|
Last Release
|
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| sensiolabs/behat-page-object-extension | 0.90 | Behat extension that helps you apply the Page Object pattern in browser acceptance tests. Provides page and element objects, reusable actions and assertions, and integrates with Mink to keep step definitions clean and maintainable. | 116 | 118 | 46 | 55K | 11 | 9.6 | 39.8 | MIT | 3 years ago | |
| laracasts/behat-laravel-extension | 0.90 | A Behat extension that boots your Laravel application inside feature tests, giving step definitions access to the container, facades, database helpers, and configuration so you can write BDD-style acceptance tests. | 260 | — | 71 | — | 25 | 11.5 | 10.0 | MIT | 8 years ago | |
| rmiller/behat-spec | 0.89 | Behat extension that integrates with PhpSpec to prevent fatal errors on missing classes or methods. Automatically generates specs and examples when Behat encounters undefined domain objects, then can run phpspec to create the code. | 52 | 53 | 6 | 8 | 6 | 2.5 | 2.7 | MIT | 10 years ago | |
| behat-extension/doctrine-data-fixtures-extension | 0.89 | Behat extension that loads Doctrine data fixtures before scenarios, making it easy to seed database state for acceptance tests. Configure fixture paths and purgers to keep test data consistent and isolated. | 20 | 20 | 7 | 267 | 2 | 0.7 | 15.7 | MIT | 6 years ago | |
| behat/behat-bundle | 0.88 | — | 64 | 65 | 16 | 12 | 0 | 0.4 | 0.7 | — | — | |
| ibexa/behat | 0.88 | Ibexa BehatBundle speeds up writing Behat tests for Ibexa DXP, with docs covering setup, running tests, available features, and extending the bundle. Install via Composer as a dev dependency. | 1 | 1 | 1 | 47K | 0 | 26.5 | 63.9 | NOASSERTION | 2 months ago | |
| halleck45/behat-tools-bundle | 0.88 | A Symfony bundle that integrates Behat into Laravel/PHP projects, providing tools and services to streamline behavior-driven testing setup. | 5 | 5 | 4 | 0 | 0 | 0.1 | — | — | — | |
| imbo/behat-api-extension | 0.88 | A Behat 3 extension that provides an easy way to test JSON-based APIs with readable Gherkin steps. Inspired by behat/web-api-extension and originally written to test the Imbo API, it simplifies HTTP request and response assertions in your test suite. | 110 | 110 | 46 | 45K | 3 | 27.5 | 43.1 | MIT | 1 week ago | |
| caciobanu/behat-deprecation-extension | 0.87 | A Behat extension that captures PHP deprecation notices raised during your scenarios and surfaces them in the test output, making it easy to track down and fix deprecated code before upgrading dependencies or PHP versions. Keeps your test suite clean and your upgrades predictable. | 22 | 23 | 6 | 2K | 1 | 0.9 | 26.3 | MIT | 6 years ago | |
| friends-of-behat/variadic-extension | 0.86 | — | 224 | 224 | 8 | 157K | 0 | 11.8 | 42.0 | MIT | 7 months ago | |
| behat/web-api-extension | 0.85 | Abandoned Behat 3 extension (never had a stable release) that provides testing for JSON APIs. It won't receive further updates, so consider alternatives for new projects; kept here for reference and legacy suites. | 108 | 110 | 108 | 731 | 16 | 4.2 | 12.1 | MIT | — | |
| dvdoug/behat-code-coverage | 0.85 | Behat Code Coverage is a Behat extension that generates PHP code coverage reports while running your test suite. It wraps php-code-coverage—the same library used by PHPUnit—so reports are familiar and interoperable with existing tooling. | 62 | 62 | 16 | 89K | 0 | 21.4 | 48.7 | BSD-2-Clause | 4 months ago | |
| friends-of-behat/test-context | 0.85 | Reusable Behat context for testing Behat extensions by running “Behat inside Behat”. Creates isolated temp projects per scenario, writes configs/features/contexts, runs a real Behat process, and lets you assert on exit codes and output. | 17 | 17 | 4 | 824 | 0 | 11.7 | 24.8 | MIT | 7 months ago | |
| behat/mink | 0.84 | — | 1,607 | 1,630 | 285 | 1M | 56 | 38.9 | 66.4 | MIT | 11 months ago | |
| friends-of-behat/mink-driver-testsuite | 0.84 | Fork of Mink DriverTestsuite updated for PHP >=7.4, Symfony >=4.4, and PHPUnit ^8.0. Use it to run Mink driver compliance tests with modern Symfony/PHP stacks. Documentation follows the original minkphp/driver-testsuite repo. | 1 | 1 | 5 | 6 | 0 | 0.2 | 8.3 | MIT | — | |
| friends-of-behat/performance-extension | 0.83 | FriendsOfBehat PerformanceExtension adds performance monitoring to Behat, measuring scenario runtimes and enforcing time limits so slow tests or regressions fail early. Useful for PHP teams wanting performance checks alongside behavioral tests. | 59 | 63 | 2 | 654 | 1 | 0.2 | 10.5 | MIT | 10 years ago | |
| friends-of-behat/mink-extension | 0.83 | — | 139 | 140 | 46 | 1M | 6 | 6.9 | 57.1 | MIT | 2 years ago | |
| behat/common-contexts | 0.83 | Abandoned Behat 2.x add-on providing reusable subcontexts with extra steps/hooks. Includes contexts like SymfonyMailerContext, DoctrineFixturesContext, and SymfonyDoctrineContext for loading fixtures, purging DB, and resetting schema in Symfony-based suites. | 115 | 115 | 34 | 2K | 0 | 0.8 | 12.9 | — | — | |
| friends-of-behat/mink-debug-extension | 0.83 | Behat extension that logs Mink-related data after every failed step and can save screenshots with a supporting driver. Configure a log directory, optional screenshots, and clean starts; especially useful for debugging CI runs like Travis. | 204 | 204 | 13 | 155K | 2 | 19.1 | 45.0 | NOASSERTION | 3 months ago | |
| bex/behat-extension-driver-locator | 0.83 | Dynamic driver/service loader for Behat extensions. Locates drivers by key in a namespace, enforces interfaces, builds and validates per-driver config trees, and loads services via DI container. Includes a DriverNodeBuilder to generate driver config nodes. | 38 | 38 | 0 | 10K | 0 | 1.7 | 33.1 | MIT | 6 years ago |
How can I help you explore Laravel packages today?