Found by reading
Pest it() and test(), PHPUnit test_ methods, Flutter testWidgets and Patrol tests — found without running anything.
devCommand reads your test files and lists every test by name, grouped by file and suite. Run one, a file, the lot, or just what failed — and jump to your editor at the failing line.
Free for everyone · macOS 14 Sonoma or later · Apple silicon and Intel
Pest it() and test(), PHPUnit test_ methods, Flutter testWidgets and Patrol tests — found without running anything.
A real project lists 19,152 tests in 3,467 files, and search still narrows them as you type.
One test, one file, the whole suite, or all the failures in a single run.
A failure shows its message and opens PhpStorm, VS Code, Cursor, Sublime Text, Xcode or Zed at the right line.
Grouped by suite — Feature, Unit, integration_test — and by file, with a Run button on each.
Runs happen in the background and results are parsed from Pest and PHPUnit’s TeamCity output, or Flutter’s JSON reporter.
Widget tests and Patrol integration tests appear the same way, and run on the device you picked.
The small things
Opening the pane never runs your suite.
Pest, PHPUnit or php artisan test, detected from the project.
Keep working while a file runs.
Only the editors you have installed are offered.
Built for projects with thousands of files.
Pest, PHPUnit, Flutter and Patrol in one pane.
Keep exploring
No account, no licence key. Point devCommand at ~/Sites and press your first command.
macOS 14 Sonoma or later · Apple silicon and Intel · Version 1.0