
Ready, set, agent
Three checks, a minute each, in your project folder. In a codespace, use its terminal.
1. The tests pass
On FridgeLister:
composer test
What counts is the end: 10 passed, nothing failed.
Tests: 10 passed (14 assertions)
Duration: 1.52s
On your own code, run the test command you normally use, such as
php artisan test, and write it down. You'll need it in the taster.
A test fails, or the command isn't found
phporcomposernot found: go back to PHP and Composer.- Fails right after
composer setup: the setup is off, not your code. The usual suspect is an old PHP:php -vmust say 8.4.1 or newer. - In a codespace: wait until the terminal has said "Ready", then try again.
2. You're on your branch
git branch --show-current
course
Says main? Run git switch -c course. See
Git: commit to it.
3. Your agent runs the tests
Start your agent in the project folder (for Claude Code, type claude)
and ask:
Say this to your agent
Run the tests and tell me how many passed.
The wording will differ, but it should look like this:
> Run the tests and tell me how many passed.
● Bash(composer test)
⎿ Tests: 10 passed (14 assertions)
● All 10 tests passed (14 assertions).
What matters: the agent ran the command itself. It will ask for permission first. Say yes, and pick "always allow" for the test command if it offers that.
Not ready if it tells you to run the tests yourself, shows the command without running it, or guesses ("probably about ten"). Check that you started it in the project folder and that it may run commands. A chat window that can't touch your files will never pass this one; see a coding agent.
All three pass?
Ready, set, go: the one-hour quality harness.
Kept in this browser. Sign in to keep it on every device.