- What is misaf/vendra-testing used for?
- misaf/vendra-testing is a Laravel/PHP testing package for Vendra that provides practical helpers for validating Vendra-powered applications. It is aimed at simplifying test setup and making feature and integration tests more reliable. It is distributed as a Composer package and is a subtree split of the Vendra Modules repository.
- How do I install misaf/vendra-testing in a Laravel project?
- Install it as a dev dependency with composer require --dev misaf/vendra-testing. Because it is a subtree split of misaf/vendra, confirm the version constraint you need and let Composer resolve it against your Laravel and PHP versions. Check composer.json to see whether it registers a service provider or is pure trait and helper code before relying on auto-discovery.
- Is misaf/vendra-testing a production dependency or dev-only?
- The package is intended for testing, so it normally belongs in require-dev rather than require. Confirm that nothing in your production dependency graph pulls it in transitively. If it stays dev-only, a bad release can break CI but should not affect production runtime.
- Which Laravel and PHP versions does misaf/vendra-testing support?
- The release artifact does not spell out supported Laravel and PHP ranges, so read composer.json and diff it between tags. Check the illuminate/* constraint and PHP floor to confirm your current Laravel minor is still admitted. A minor release may add support for a newer framework version while still preserving older ones, but verify it did not drop yours.
- What changed between misaf/vendra-testing v1.11.0 and v1.12.3?
- The published window moved from v1.11.0 to v1.12.3, a minor bump plus patches that SemVer declares backwards compatible. The release artifact contains no release notes, only a compare link, so inspect the commit diff, tag history, and composer.json changes directly. Pay particular attention to assertion or mocking defaults, new required config keys, and any change to supported Laravel or PHP ranges.
- Does misaf/vendra-testing publish config, migrations, or service providers?
- This needs to be confirmed from the package source and composer.json rather than assumed. Testing packages sometimes ship only traits and helpers, while others register a service provider or publish config that could collide with your test bootstrap. Review any publishables, migrations, or provider registrations before adding it to a shared test suite.
- Is misaf/vendra-testing safe to use in CI and production?
- If used strictly in require-dev, the risk is mostly limited to CI and test reliability rather than production. Check whether the package makes network calls, writes files, or embeds credentials in fixtures, or whether it is purely in-process. Also verify that helper changes cannot silently flip test outcomes in the passing direction.
- How do I upgrade misaf/vendra-testing from v1.11.x to v1.12.x safely?
- Stay pinned to 1.11.x in the lockfile until you have reviewed the diff. Cut a branch and run composer require --dev misaf/vendra-testing:^1.12, capturing any resolver conflict with your existing Laravel constraint as a finding. Run the full suite and compare coverage against the 1.11.x baseline; equal pass counts with changed coverage is a signal that helper behavior moved.
- Are there alternatives to misaf/vendra-testing for testing Vendra applications?
- misaf/vendra-testing is a subtree split of misaf/vendra, so the primary alternative is using Vendra's own test utilities or writing custom helpers in your application. Search Packagist for other Vendra-related testing packages and compare their Laravel support and release activity. Because this package is narrowly scoped, replacing it may be straightforward if maintenance becomes a concern.
- Who maintains misaf/vendra-testing and how active is the project?
- The package is maintained as part of the misaf/vendra project and published via subtree split. The v1.11.0 to v1.12.3 window shows three releases without descriptive notes, which suggests low documentation discipline and makes the bus factor worth checking. Review the GitHub issue tracker, response history, and release cadence before adopting it broadly.