thesis / testo-plugin
Testo plugins for thesis packages: tests on the virtual time of thesis/async, PHP errors as failures.
Fund package maintenance!
Requires
- php: ^8.5
- php-64bit: *
- internal/container: ^1.1
- testo/testo: ^0.10.29
- thesis/async: ^0.1
Requires (Dev)
- testo/assert: ^0.1.17
- testo/test: ^0.1.8
- thesis/time: ^0.3
Suggests
None
Provides
None
Conflicts
None
Replaces
None
This package is auto-updated.
Last update: 2026-11-17 08:51:08 UTC
README
Plugins for Testo to test code built on thesis packages.
Installation
composer require --dev thesis/testo-plugin
Requires 64-bit PHP 8.5+.
Virtual time
VirtualTimePlugin and the #[VirtualTime] attribute run a test in its own Thesis\Async\VirtualTime\run()
of thesis/async: the clock jumps to the next timer whenever nothing can run,
so delay(hours(1)) is over at once and durations can be asserted exactly. How the virtual clock behaves is described
in the README of thesis/async.
Every test of a suite, with the plugin in testo.php:
use Testo\Application\Config\ApplicationConfig; use Testo\Application\Config\SuiteConfig; use Thesis\TestoPlugin\VirtualTimePlugin; return new ApplicationConfig( suites: [ new SuiteConfig(name: 'unit', location: [__DIR__ . '/tests'], plugins: [new VirtualTimePlugin()]), ], );
Or only some, with the attribute on a test class or a test:
use Testo\Assert; use Testo\Test; use Thesis\Async\Instant; use Thesis\TestoPlugin\VirtualTime; use function Thesis\Async\delay; use function Thesis\Time\hours; #[Test] final class HeartbeatTest { #[VirtualTime] public function waitsAnHour(): void { $start = Instant::now(); delay(hours(1)); Assert::equals(Instant::now()->since($start), hours(1)); } }
The lifecycle hooks of a test (#[BeforeTest], #[AfterTest]) run on its clock, and every data set gets a clock
of its own. A test that has the attribute in a suite with the plugin is not wrapped twice.
PHP errors
PHP only prints a warning, a notice or a deprecation, and the test passes. PhpErrorsPlugin throws one
as ErrorException where it happens, in the test and in the tasks it starts alike, so the test fails
and the trace points at the cause. An error suppressed by @ is left alone, and a handler that the test sets itself
sees the errors first.
Every suite, with the plugin in testo.php:
use Testo\Application\Config\ApplicationConfig; use Testo\Application\Config\SuiteConfig; use Thesis\TestoPlugin\PhpErrorsPlugin; return new ApplicationConfig( suites: [ new SuiteConfig(name: 'unit', location: [__DIR__ . '/tests']), ], plugins: [new PhpErrorsPlugin()], );