Testing
Try the guestbook's behavior, give an agent useful evidence, and verify the fix beside the work.
Check the guestbook the way you would check your own project: run a quick check, try the behavior, and hand the evidence to an agent. Keeping the terminal, preview, and conversation together makes it easier to connect a failure to the change that caused it.
Use the example project, or follow the same recipe with your project's existing test command.
Run the check you already have
Open a terminal pane in the guestbook directory. If Node.js is installed, its fastest available check is:
node --check app.jsSuccess normally prints nothing and exits with code 0. This checks JavaScript
syntax only. In your own project, use its real test command here; the guestbook
has no npm test script or dependencies to install.
Test the behavior
Open index.html in a browser preview.
For each check, compare what happened with what you expected:
- Empty notes: enter a name, leave the note empty, and choose Leave a note. Expect the form to require a note and the list to stay unchanged. Also try a note containing only spaces; it should not be saved.
- Character limit: paste more than 280 ordinary letters into the note field. Expect it to stop at 280. If you completed the character-counter exercise, also check that its count updates when you type, paste, and delete text.
- Saving and persistence: enter a name and a distinctive note, and submit. Expect the note at the top, the form to clear, and the note to remain after you reload the page.
Notes belong to the browser's local storage. A note saved in hob's preview is not expected to appear in another browser, and the reverse is also true.
You can also ask the agent to run these checks in the preview while you watch:
Ask your agent
The agent uses real input in the page. You can take control at any time; see Agents on web pages.
Hand the evidence to an agent
When a behavior differs, record the exact input, expected result, actual result, and where you tried it. Replace the bracketed fields before sending this prompt:
Ask your agent
Keep useful output beside the conversation. The agent can show the changed file or point at the result while you decide whether the behavior is right. If the problem only occurs inside the preview, compare with another browser before changing app code.
Rerun both checks
Rerun the same command and repeat the behavior that failed with the same input. Then try the other behaviors above to check for regressions. Passing syntax alone does not establish that saving, reset, or persistence works.
Review the diff before accepting the fix. Ask the agent to name anything it could not verify, so you know what remains to try.
Keep the useful result
Bookmark the output when a failure or baseline will help later. Save a repeated check as an automation to keep its runs and results in the project. The check-and-review workflow builds on this same guestbook without turning a syntax check into a claim of full test coverage.
For agents
Use the actual terminal ID from hob pane list, and confirm its working
directory is the project you are checking:
hob message --pane <terminal-id> --text "node --check app.js" --wait
hob pane view <terminal-id> --cmd <command-id>The send result supplies the command ID for the second command. A command sent this way appears as an attributed block in that terminal, where the person can inspect or rerun it. A backend's own shell-tool calls stay in its conversation; they do not automatically create command blocks in a hob terminal.
Report the exit status and observed behavior separately. If you cannot try the browser behavior, say so and give the person the exact remaining check.