- Can I use this package with Laravel’s default PHPUnit 10.x, or do I need PHPUnit 8.x?
- This package requires PHPUnit 8.x, but Laravel’s default PHPUnit 10.x can coexist if you configure a separate `phpunit.xml` for Mink driver tests. Override the bootstrap and PHP settings in the test suite’s config file to avoid conflicts. Check your `composer.json` for version constraints.
- How do I integrate this test suite into an existing Laravel Behat/Mink setup?
- Install the package via Composer, then configure Behat to include the driver test suite’s contexts. Add a `behat.yml` snippet to run the test suite against your Mink drivers (e.g., Selenium2 or Goutte). No Laravel-specific changes are needed—it works with Mink’s framework-agnostic architecture.
- Does this package support Laravel-specific Mink drivers like Dusk or Pest?
- No, this package is designed for generic Mink drivers (e.g., Selenium2, Goutte, Cypress). Laravel’s Dusk or Pest + BrowserKit are alternatives and don’t require this test suite. Use this only if you rely on Behat/Mink for functional testing.
- Will this package break if I upgrade Laravel to a newer version?
- This package depends on Symfony 4.4+ and PHP 7.4+, so it may conflict with newer Laravel versions if they drop support for those dependencies. Test in a staging environment first, and use `composer why-not` to check for version mismatches. Laravel’s default PHPUnit 10.x may also need configuration tweaks.
- What Mink drivers are officially supported by this test suite?
- The test suite validates compliance for core Mink drivers like Selenium2, Goutte, and potentially others (e.g., Cypress). Check the [original Mink documentation](https://github.com/minkphp/driver-testsuite) for a full list. If your driver isn’t listed, test it manually or contribute to the fork.
- Is this fork actively maintained, or should I use the original minkphp/driver-testsuite?
- This fork is a static update for PHP 7.4+ and Symfony 4.4+, with no guarantees of future updates. The original `minkphp/driver-testsuite` may still work if your stack supports older PHP/Symfony versions. Monitor the repo for sync announcements or consider contributing fixes.
- How do I run the Mink driver tests in my Laravel CI pipeline (e.g., GitHub Actions)?
- Add a step to execute Behat with the driver test suite’s config file. Example for GitHub Actions: `run: vendor/bin/behat -c behat-driver.yml`. Ensure your CI environment has the required PHP extensions (e.g., `php-xml`, `php-curl`) and dependencies installed.
- Can this package replace manual testing of Mink drivers in production?
- No, this test suite validates driver compliance but doesn’t replace manual testing for edge cases or production-specific scenarios. Use it as a safety net for regression testing, not as a standalone QA solution.
- What are the risks of adding symfony/browser-kit as a dependency via this package?
- The package pulls in Symfony BrowserKit, which may introduce version conflicts if your Laravel app uses a different Symfony version. Audit your `composer.json` for conflicts, and use `composer why symfony/browser-kit` to identify dependencies. Test thoroughly in a staging environment.
- Are there alternatives to this package for testing Mink drivers in Laravel?
- Yes, consider Laravel Dusk for browser testing or Pest + BrowserKit for lightweight functional tests. If you’re committed to Behat/Mink, the original `minkphp/driver-testsuite` (if compatible) or custom PHPUnit tests for drivers are alternatives. Evaluate based on your stack’s needs.