hypervel / testbench

v0.3.26 2026-01-16 16:16 UTC

Requires

• php: ^8.2
• hypervel/framework: ^0.3
• mockery/mockery: ^1.6.10
• phpunit/phpunit: ^10.0.7
• symfony/yaml: ^7.3
• vlucas/phpdotenv: ^5.6.1

MIT

• Albert Chen

• php
• TestBench
• swoole
• hyperf
• hypervel

Published on Packagist.org on 2026-08-14 06:30 UTC

README

Documentation: https://hypervel.org/docs/testbench

Differences From Laravel

Laravel packages require orchestra/testbench, which installs Orchestra Testbench Core, Workbench and Sidekick. hypervel/testbench contains Testbench Core itself under the Hypervel\Testbench namespace. The Sidekick helpers that Testbench relies on are provided by Testbench or the framework; Sidekick's other helpers are not ported. Testbench Core's Workbench support is included, while Orchestra Workbench's authentication pages, preview login helpers and workbench:* command aliases are in the separate hypervel/workbench package, which Testbench suggests but does not install.

Hypervel applies every #[WithConfig] value before service providers register. Orchestra's deferred mode is intentionally omitted because configuration is process-global state shared by Hypervel's long-lived Swoole worker. When a package provider uses shallow configuration merging, a nested key replaces that package option's defaults. Tests that need a post-boot value, or a nested value alongside the package defaults, should set it explicitly in the test body.

Hypervel does not forward the parent Testbench CLI application's full runtime environment to package:test subprocesses. In package-test mode, package and workbench environment files are copied into the child runtime application, while shell or CI environment variables, PHPUnit XML values, and Testbench YAML env values continue to reach package-test child processes through their normal channels.

The package:test command uses -c as the shortcut for --configuration, matching PHPUnit and the application's test command. Orchestra's unused --custom-argument flag is omitted.

Testbench writes boolean environment values as true and false instead of (true) and (false), so libraries that read environment variables directly can interpret them. Laravel-style env() behavior is unchanged.

Hypervel does not use Orchestra's TESTBENCH_APP_BASE_PATH channel. Each process owns its runtime application identity through BASE_PATH, remote child processes receive the current worker clone through TESTBENCH_BASE_PATH, and APP_BASE_PATH remains the explicit user override.

Hypervel includes root package discovery metadata when a package:test worker builds the Testbench package manifest. Orchestra's persistent skeleton can be seeded by the parent Testbench CLI process, while Hypervel's per-worker runtime skeletons may build their manifests directly inside PHPUnit / ParaTest workers.

Hypervel's serve command creates and removes the Workbench sync links itself, while Orchestra applies them through the optional Workbench package. Each command gets its own copy of the default skeleton, so package:sync-skeleton only syncs custom skeletons. An existing file or directory that isn't a symlink is never replaced at a to path outside that copy; Orchestra deletes it. Existing symlinks are still replaced. See Syncing Workbench Directories.

Orchestra Testbench resets framework static state from its test case. Hypervel resets it after each test from the Hypervel\Testing\PHPUnit\AfterEachTestExtension PHPUnit extension, so a package's phpunit.xml file needs to register it. See Test State Cleanup.

Pest integration is not supported in Hypervel 0.4. Use PHPUnit test classes; WithFixtures does not resolve Pest test files. See the testing documentation.

Ported from:

• https://github.com/orchestral/testbench-core
• https://github.com/orchestral/testbench