- Is sylius-labs/suite-tags-extension a Laravel package for tagging Eloquent models?
- No. Despite the name and the tagging-oriented description, source assessment identifies it as a Behat Testwork extension that routes Gherkin scenarios into named suites such as api, ui, or admin based on tags in behat.yml. It has no service provider, Eloquent model, migration, or runtime footprint in a Laravel application. It only affects the acceptance-test layer, and only if your team runs Behat.
- How do I install sylius-labs/suite-tags-extension in a Laravel app?
- Install it as a dev dependency with composer require --dev sylius-labs/suite-tags-extension, add the extension block under extensions: in behat.yml, and tag your feature files. There is no config publishing, package discovery, or application bootstrapping involved. Treat it as CI test tooling rather than an application capability.
- What configuration keys does SuiteTagsExtension use in behat.yml?
- There is no documentation beyond the source, so read the extension class and any Configuration.php before trusting snippets. The exact key names, whether suite_tags, tags, or nested maps are used, must be confirmed from configure(). A mis-keyed block can fail silently in Behat and turn a short trial into a long debugging session.
- Does this package provide tag entities or Doctrine mappings for products, orders, or customers?
- No. That framing does not match the primary source assessment, which finds a single Behat extension class rather than entities, Doctrine mappings, or a service layer. It does not attach labels to application resources or provide querying. If you need entity tagging in Sylius or Laravel, evaluate a different package.
- Which Behat versions are supported by this extension?
- The extension was written against Behat 3.x and shows no activity. Behat's Suite and Filter internals have moved across major versions, so an upgrade can break the filter without a clear error. Pin Behat explicitly in composer.json and treat any Behat major bump as a re-evaluation trigger.
- Will it work with PHPUnit or Pest instead of Behat?
- No. It integrates only with Behat's extension and suite-filter layer. Teams running PHPUnit or Pest alone get zero value from this package. Use native PHPUnit groups or test suites for equivalent scenario selection.
- Why do I get zero scenarios matched in CI but the same command passes locally?
- The suite filter ANDs with CLI --tags, so combining suite routing and tag arguments can produce zero matched scenarios. Check both your behat.yml suite tags and any --tags options in the CI command. Remove one filter or adjust tags so the intersection is not empty.
- Is sylius-labs/suite-tags-extension safe to use in production?
- It is dev-time test tooling with no runtime footprint and no data schema change. The blast radius is confined to CI, and rollback is simply deleting the YAML block and the dev dependency. It does not deliver tagging features to end users, so frame it to stakeholders as test infrastructure.
- What are alternatives to this extension for splitting Behat suites?
- Native Behat --tags, multiple profiles, or separate suite configurations in behat.yml can often achieve the same routing. Evaluate whether suite routing solves a measured problem such as CI wall-clock or duplicated config that built-in filters would not. This extension is a narrow convenience, not a required dependency.
- Is this package maintained, and can I vendor it if upstream goes dark?
- The package has 2 stars, 0 dependents, no documentation beyond source, and little activity. Check the license before adopting it. The code surface is small, likely one extension class, so vendoring inline is a viable fallback if upstream becomes unavailable.