Weave Code
Testing Laravel Package
orchestra/testing
Testing utilities for Orchestra Platform and Laravel packages, providing test case helpers, package bootstrapping, and assertions that simplify unit and integration testing for extensions and applications built on PHP.
Orchestra Testing provides testing utilities for Laravel applications built on the Orchestra Platform. It extends Laravel’s testing capabilities with platform-aware helpers, reducing boilerplate around bootstrapping, configuration, and assertions so you can focus on reliable extension and application tests.
- Platform-aware base test case and bootstrap helpers
- Support for testing Orchestra extensions and packages
- Simplified database and fixture setup
- HTTP/route and response assertion utilities
- Consistent test environment configuration
Frequently asked questions about Testing
- What is orchestra/testing used for?
- It is a dev-only testing harness for Laravel applications and extensions built on the Orchestra Platform. It extends Laravel's TestCase to boot an Orchestra-aware application, register extension service providers, load manifests, and run migrations. It also provides HTTP, route, and response assertion helpers so extension and application tests need less boilerplate. It has no production runtime footprint and no value outside the Orchestra ecosystem.
- How do I install orchestra/testing?
- Install it with composer require --dev orchestra/testing and pin it alongside the matching orchestra/testbench and Orchestra Platform version, bumping them as one unit. Then extend the base test case in a project-level TestCase and rely on the helper traits for extension install, uninstall, and manifest loading. Because the only listed release note (v5.0.0) cites Laravel Framework v7, verify compatibility with composer why-not on a throwaway branch before wiring it into shared CI.
- Which Laravel versions does orchestra/testing support?
- The documented release history is thin: v5.0.0 cites Laravel Framework v7 support. The package does not advertise a current support matrix beyond that, so treat compatible PHP, Laravel, PHPUnit, Testbench, and Orchestra Platform versions as unconfirmed until tested. Validate them empirically on a disposable branch, using a CI matrix with one job per supported Laravel major to catch PHPUnit API and bootstrap drift.
- Do I need orchestra/testing for a plain Laravel app?
- No. For plain Laravel services, native Laravel testing, PHPUnit or Pest, and a small internal base TestCase are the correct answer. Adding orchestra/testing buys an unmaintained dependency and an unproven harness for zero benefit when Orchestra Platform is not already a dependency. Adopt it only where Orchestra Platform is already part of the stack.
- How do I test an Orchestra extension with orchestra/testing?
- Extend the package's platform-aware base test case in a project-level TestCase and use the helper traits to install and uninstall the extension and load manifests. From there, assert routes, responses, and migrations much like a normal Laravel feature test. Centralize the required traits, database configuration, and migration loading so lifecycle behavior stays consistent across all test files.
- How should I set up the base test case from orchestra/testing?
- Create one project-level base test case that extends the Orchestra base case, applies the required traits, and centralizes database configuration and migration loading. Have every test file extend that project class rather than the vendor class directly, so reverting to Testbench plus native tooling stays a one-line base class swap. Convert one boot test, one route test, and one migration test first, then measure boilerplate removed and CI wall-clock delta before converting the rest.
- Does orchestra/testing handle database migrations and fixtures in tests?
- Yes, it advertises simplified database and fixture setup alongside manifest loading and platform-aware bootstrapping. Confirm that the manifest and migration path mirrors a real install on a disposable branch before trusting it broadly. Watch for stale manifest caches and global state leaking between tests, which are the usual failure modes for this kind of bootstrap harness.
- Can orchestra/testing cause flaky or order-dependent tests?
- It can. Known risk areas include legacy bootstrap behavior, stale manifest caches, deprecated PHPUnit APIs, and global state leaking between tests, which produces order-dependent failures. All of it surfaces in CI rather than production, so the blast radius is limited, but a flaky harness can still block releases. Run tests in random order and keep any global phpunit.xml bootstrap changes isolated to catch leaks early.
- What are the alternatives to orchestra/testing?
- The main alternative is orchestra/testbench combined with native Laravel tooling, PHPUnit or Pest, and a small internal base TestCase. For projects that do not depend on Orchestra Platform, those options are the correct answer outright. Before adopting orchestra/testing, compare the scaffolding lines it actually removes against that combination and measure the CI wall-clock delta.
- Is orchestra/testing still maintained and safe to use?
- It is dev-only, so it cannot reach production runtime, which limits concern to CI supply chain and license review. External validation is weak: it shows score 0.3, no stars, zero dependents, and a thin release history, suggesting a possibly stale line. Name an upstream owner for compatibility, document the confirmed version matrix, and keep revert cost at one line by extending a single project-level base test case.
Weaver
How can I help you explore Laravel packages today?