- What Laravel versions does JobBoy Test Pack support? Does it work with Laravel 10/11?
- The package doesn’t explicitly declare Laravel version constraints in its documentation or composer.json. You must verify compatibility by checking JobBoy’s own Laravel version requirements (e.g., if JobBoy uses Laravel 10, ensure this package doesn’t pull in Laravel 11 dependencies). Always pin exact versions in your `composer.json` to avoid conflicts.
- How do I add JobBoy Test Pack to my Laravel project? Is it a dev-only dependency?
- Add it as a dev dependency via Composer: `composer require --dev dansan/jobboy-test-pack`. It’s designed for test environments only—no runtime impact. Follow the [documentation](https://github.com/danielsan80/jobboy-doc/blob/master/doc/jobboy-test-pack.md) for setup instructions specific to JobBoy repositories.
- Does this package replace Laravel’s built-in testing helpers or spatie/laravel-test-factories?
- No, it’s not a replacement but a complement. JobBoy Test Pack standardizes *JobBoy-specific* test utilities (e.g., job assertions, mocks) across repositories, while Laravel’s helpers or spatie packages handle general testing needs. Use both for full coverage.
- Can I use this package if my project isn’t part of the JobBoy ecosystem?
- No, this package is *exclusively* for JobBoy repositories. It assumes JobBoy’s testing conventions (e.g., job structures, assertions) and won’t work for generic Laravel projects. Alternatives like `spatie/laravel-test-factories` are better for non-JobBoy use cases.
- What if my JobBoy repo already has custom test assertions or factories? Will they conflict?
- Potential conflicts exist if your repo’s test logic overlaps with the package’s utilities. Audit your test suite for duplicate assertions, factories, or mocks before integrating. The package prioritizes JobBoy’s standardized approach—custom code may need refactoring.
- How often is this package updated? Is it actively maintained?
- The package lacks recent GitHub activity, raising maintenance concerns. Review the [documentation](https://github.com/danielsan80/jobboy-doc) for version history and check JobBoy’s roadmap. Pin to a specific version (e.g., `1.0.0`) and plan for forking if critical bugs arise.
- Does JobBoy Test Pack include its own test suite to validate reliability?
- There’s no evidence of a test suite for the package itself. Rely on its adoption by JobBoy repositories as a proxy for stability. If reliability is critical, test its utilities in a staging environment before full integration.
- Can I extend the package with custom test utilities, or is it locked down?
- The package appears rigid—it’s designed to enforce JobBoy’s testing conventions. Custom extensions would likely require forking. Review the [documentation](https://github.com/danielsan80/jobboy-doc) for undocumented APIs or contact the maintainer for guidance.
- What PHPUnit/Pest features does this package provide? Does it include mocks, factories, or assertions?
- The package centralizes JobBoy-specific test utilities, likely including job-related assertions (e.g., `assertJobDispatched()`), mocks for job queues, and possibly shared factories. Check the [documentation](https://github.com/danielsan80/jobboy-doc) for a full list—it may also wrap Laravel’s Testing facade for JobBoy use cases.
- Will using this package slow down my test suite or increase memory usage?
- No runtime impact is expected, as it’s a dev-only dependency. However, shared test utilities might add minor overhead if they load additional services (e.g., database transactions). Profile your test suite post-integration to confirm performance.