Mink Debug Extension Laravel Package

Product Decisions This Supports

• Roadmap and QA tooling investment: Decide whether Behat + Mink remains a supported BDD/testing layer for Laravel projects. If yes, this extension is a low-cost observability add-on for failed steps, not a new platform dependency.
• Build vs. buy: Prefer adopting and pinning this small OSS extension over building custom Behat hooks for failure logs and optional screenshots. Build internally only if requirements exceed simple failed-step artifacts or if the package becomes unsupported.
• Test observability feature: Improve CI and local debugging by generating HTML logs after failed Mink steps and screenshots with supporting drivers. This can reduce mean time to diagnose flaky browser/HTTP tests.
• Use cases: CI failure triage, local debugging of Behat/Mink scenarios, QA onboarding, flaky test investigation, and capturing post-failure context for engineering review.
• Scope boundary: Treat as a dev/test-only Composer dependency. It does not replace PHPUnit, Pest, Laravel Dusk, or application-level observability, and it does not require Laravel service-provider integration.
• Risk decision: License is NOASSERTION, dependents are zero, and ecosystem activity is limited. Adopt only after legal review and with a maintenance/fallback plan; do not position it as a strategic platform bet.

When to Consider This Package

• Consider adoption when: the team already uses Behat + Mink; failed-step diagnostics are missing; CI artifacts such as HTML logs and screenshots would materially speed triage; the team wants minimal behat.yml configuration; and engineering can pin versions, own upgrades, and accept community-supported OSS.
• Consider a limited pilot when: Behat is used only for a subset of UI/integration tests and the organization wants to validate debugging value before broader BDD investment.
• Look elsewhere when: the stack uses Laravel-native PHPUnit/Pest/Dusk instead of Behat/Mink; the team needs vendor support, SLA, or active maintenance guarantees; advanced browser tracing/video/devtools are required; legal cannot accept license ambiguity; or the zero-dependent ecosystem signals unacceptable long-term risk.
• Look elsewhere when: debugging needs can be met by Behat verbose output, Dusk screenshots, or existing CI test reports. This package should not be adopted solely to justify a Behat migration.

How to Pitch It (Stakeholders)

Executive summary: This is a small, dev-only OSS extension that captures logs and optional screenshots after failed Behat/Mink steps. It can improve QA feedback and reduce debugging time at low implementation cost, but it is not a strategic platform dependency and does not affect customer-facing runtime. Adopt only if Behat is already part of the testing stack, legal clears the NOASSERTION license, and engineering pins the version with a fallback plan.

Engineering summary: Add friends-of-behat/mink-debug-extension as a Composer dev dependency, configure FriendsOfBehat\MinkDebugExtension with a log directory and optional screenshot/clean-start settings, and publish artifacts from CI failed-step runs. There is no Laravel service provider or runtime integration. Main risks are limited maintenance signals, zero dependents, and license ambiguity; mitigate by isolating it to Behat profiles, pinning versions, limiting CI artifact retention, and remaining ready to replace it with custom Behat hooks if needed. It complements—but does not replace—PHPUnit, Pest, or Dusk.