Choose the right kind of test
A unit test checks a small piece, an integration test checks cooperating pieces, and a browser test checks a user journey. Manual review catches visual and language issues too.
What is it?
A unit test checks a small piece, an integration test checks cooperating pieces, and a browser test checks a user journey. Manual review catches visual and language issues too.
Why it matters
Evidence connects an implementation to its requirements.
When to use it
Before accepting or releasing a change.
How to do it
- Read the explanation and identify the files or environment involved.
- For a search feature, define a text-matching unit case, a data-loading integration case, and a browser case that types a term and opens a result.
- Compare the result with the verification criteria below. Record what worked and what remains unclear.
Worked example
For a search feature, define a text-matching unit case, a data-loading integration case, and a browser case that types a term and opens a result.
Try it yourself
Repeat the exercise with your own wording or a second sample. Use the smallest change that demonstrates the idea.
Prompt builderVerify your result
Each test protects a different meaningful failure instead of repeating the implementation.
Common mistakes
Measuring quality only by test count. Prefer important behavior and failure coverage.
How to recover
Stop at the first unexpected result. Preserve your current work, re-check the named file or environment, and repeat only the failing step. Ask for an explanation if the recovery is unclear.
Official references
Product interfaces and access can change. Use the linked official guide for current installation and account requirements.
OpenAI · Quickstart ↗Source review: 2026-09-16