Mbt Bundle Laravel Package

Product Decisions This Supports

• Test automation strategy: scripted E2E vs. model-based testing (MBT). This package is the PHP-side core that connects a Symfony application to Sicope Model, a graphical MBT tool. It supports the decision of whether to model high-variability user journeys (checkout, onboarding, permissions, multi-step wizards) as state machines and generate test sequences, instead of hand-writing an ever-growing list of end-to-end scripts.
• Build vs. buy vs. borrow. MIT-licensed and free to adopt, but 18 stars and a last release of July 2022 mean the realistic decision is "adopt the technique, own the code." The buy decision is really borrow the concepts and fork the library, not take a dependency.
• Where to spend regression coverage. Best suited to flows where path combinations explode and scripted suites become brittle. Not suited to broad UI/a11y/visual coverage — that stays with whatever E2E framework you already run.
• Roadmap input for QA tooling and platform work. If a spike succeeds, it justifies investment in shared models as living specifications, CI hooks to generate and execute suites, and review process for model changes — that's platform roadmap work, not a library decision.
• Framework and hiring constraints. This is a Symfony bundle, not a Laravel package. Adoption implicitly favors a Symfony-centric stack and constrains who can maintain it.

When to Consider This Package

Adopt (or, more precisely, prototype) when:

• Your application is Symfony-based and its riskiest behavior lives in stateful, combinatorial flows where model-derived sequences add coverage that scripted tests miss.
• You have a team willing to own a fork: pin PHP/Symfony constraints, patch compatibility yourself, and accept that upstream fixes may never arrive.
• You can run the companion Sicope Model graphical tool in your workflow — the bundle is the execution core, not a standalone test runner, so its value is gated on that second moving part.
• You're treating this as a time-boxed R&D spike with a clear kill criterion, not a production dependency with an implied support contract.

Look elsewhere when:

• You're Laravel-first; there is no first-class integration and you'd be adapting a Symfony bundle.
• You need vendor support, SLAs, or a security review trail — no commercial backing exists.
• You need current PHP/Symfony support; a 2022 release predates recent majors and will need patching.
• Your hiring and CI ecosystem is standardized on Playwright/Cypress/Selenium and you don't want a technique-specific skill on the critical path.
• The flows under test are simple or highly UI-dependent, where conventional tests are cheaper to write and read.

How to Pitch It (Stakeholders)

For executives: This is a free, MIT-licensed PHP library that supports model-based testing — describing an application as a state machine and generating test cases from it rather than hand-writing each one. The strategic appeal is coverage on complex, high-variability user journeys, where scripted tests are expensive to maintain. The caveat is support: the project is small (18 stars) and its last release was July 2022, so it carries real maintenance and abandonment risk. Recommendation is a low-cost, time-boxed spike on one high-value flow, scoped to prove coverage gains before any broader commitment. Do not position it as a replacement for the existing test stack, and do not adopt it where a supported vendor dependency is required.

For engineering: The bundle is the PHP core that plugs a Symfony app into Sicope Model's test-generation engine. Expect to pin versions, fork for compatibility, and contribute patches upstream or internally. The durable value is the modeling discipline and generated sequences; even a failed spike leaves behind a clearer behavioral spec of your riskiest flow. Start by checking Symfony/PHP constraint compatibility and confirming the graphical tool fits your CI workflow before writing models.