| layout | title | description | image | llms | hero | features | ||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
home |
Testo — Modern PHP Testing Framework |
PHP testing framework without TestCase inheritance. Clean OOP, middleware architecture, PSR-14 events, Assert/Expect facades. |
/images/og-image.jpg |
false |
|
|
::: warning 🚧 Work in Progress Testo is still under active development and not ready for production use. Feel free to explore and experiment, but don't rely on it for real projects yet.
Want to support the project? Star the repo or become a sponsor. :::
Assertion functions are split into semantic groups:
Assert::facade — assertions, executed immediatelyExpect::facade — expectations, deferred until test completion
Pipe syntax with type grouping keeps code concise and type-safe.
<template #assert>
use Testo\Assert;
// Pipe assertions — grouped by type
Assert::string($email)->contains('@');
Assert::int($age)->greaterThan(18);
Assert::file('config.php')->exists();
Assert::array($order->items)
->allOf(Item::class)
->hasCount(3);<template #expect>
use Testo\Expect;
// ORM should stay in memory
Expect::leaks($orm);
// Test fails if entities are not cleaned up
Expect::notLeaks(...$entities);
// Output validation
Expect::output()->contains('Done');<template #expectException>
// Have you seen this anywhere else?
Expect::exception(ValidationException::class)
->fromMethod(Service::class, 'validateInput')
->withMessage('Invalid input')
->withPrevious(
WrongTypeException::class,
static fn (ExpectedException $e) => $e
->withCode(42)
->withMessage('Field "age" must be integer.'),
);<template #expectAttr>
/**
* You can use attributes for exception expectations
*/
#[ExpectException(ValidationException::class)]
public function testInvalidInput(): void
{
$input = ['age' => 'twenty'];
$this->service->validateInput($input);
}Write tests the way that fits your style.
- Tests can be classes, functions, or even attributes right in production code (Inline Tests).
- Classes don't need to inherit from a base test class. Code stays clean.
- Test discovery by naming conventions or explicit attributes.
<template #declare-class>
// Explicit test declaration with #[Test] attribute
final class OrderTest
{
#[Test]
public function createsOrderWithItems(): void
{
$order = new Order();
$order->addItem(new Product('Bread'));
Assert::int($order->itemCount())->equals(1);
}
}<template #declare-function>
// Explicit test with #[Test] attribute
// or "test" prefix in function name
#[Test]
function validates_email_format(): void
{
$validator = new EmailValidator();
Assert::true($validator->isValid('user@example.com'));
Assert::false($validator->isValid('invalid'));
}
function testEmailValidator(): void { ... }<template #declare-convention>
// "Test" suffix on class and "test" prefix on methods
final class UserServiceTest
{
public function testCreatesUser(): void
{
$user = $this->service->create('john@example.com');
Assert::string($user->email)->contains('@');
}
public function testDeletesUser(): void { /* ... */ }
}<template #declare-inline>
// Test the method right in your code
// Convenient for simple cases
final class Calculator
{
#[TestInline([1, 1], 2)]
#[TestInline([40, 2], 42)]
#[TestInline([-5, 5], 0)]
public function sum(int $a, int $b): int
{
return $a + $b;
}
}Native plugin for PhpStorm and IntelliJ IDEA.
Full-featured workflow: run and re-run from gutter icons, navigation between tests and code, debugging with breakpoints, test generation, results tree.