Write criteria you can observe
A requirement that the website should feel simple is difficult to approve objectively. Instead, describe how a new visitor should find the scope of a service, open its inquiry route and understand the information requested. Define where the test starts and what outcome counts as success.
For a fictional installation business, test the journey from a service page to a complete quotation request. Use fictional details and an agreed test address. Check both the browser feedback and the intended receiving system. Coordinate with the recipient so the exercise is not mistaken for a genuine customer inquiry.
Test the failure paths too
Try missing required fields, an invalid email address and a failed request if the test environment supports it. The visitor should understand what needs correcting. A form that displays success when delivery has failed should not be accepted as a working contact journey.
Include a narrow mobile viewport, enlarged text and keyboard navigation. Essential controls need visible focus and must be reachable without a mouse. Automated accessibility checks can identify some defects, but they cannot replace someone actually completing the tasks.
| Task | Expected result | Record |
|---|---|---|
| Send a test inquiry | Accurate feedback and verified receipt | Time and recipient |
| Edit a phone number | Correct number in the intended preview | Page and user role |
| Switch language on a service page | Real equivalent or clear fallback | Starting and final URL |
| Navigate by keyboard | Visible focus and reachable controls | Device and browser |
Let the receiving editor do the work
A developer’s demonstration shows what the developer can do. A better handover exercise lets the future editor change a heading, replace an allowed image and find the preview. Test the permissions the editor will actually receive rather than granting administrator access to make the exercise easier.
Record what remains outside the test. Payments, email delivery or a third-party integration may need separate accounts and a dedicated test. Mark an unavailable integration as an unresolved dependency rather than assuming it passed because the surrounding page looks complete.
- Keep the starting address, steps, expected result and actual result.
- Separate blocking defects from minor issues.
- Give each issue an owner and a follow-up check.
- Do not treat testing as permission to publish to production.
Approve a specific version
Tie the acceptance record to an identifiable preview version. A corrected contact function needs testing again; unrelated assessments need not be repeated when nothing affecting them has changed. Changes to shared navigation may, however, require several page types to be checked. Confirm which issues are resolved, explicitly accepted or still blocking delivery. Approval then becomes a comprehensible decision rather than a short message saying the site looks nice.