imbahub
Menu +
EN
Talk to us
IMBAHUB / Knowledge & guides

How do you know the new website is ready?

An acceptance test compares the delivery with what you commissioned. Choose real tasks, state what should happen and record the outcome. An attractive homepage does not prove that an enquiry arrives or that your editor can make the next change.

Make approval testable

  1. Define

    State the task and observable result.

  2. Exercise

    Test as a customer and an editor with the intended permissions.

  3. Confirm

    Record issues and retest the corrections.

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 enquiry 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 enquiry.

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.

TaskExpected resultRecord
Send a test enquiryAccurate feedback and verified receiptTime and recipient
Edit a phone numberCorrect number in the intended previewPage and user role
Switch language on a service pageReal equivalent or clear fallbackStarting and final URL
Navigate by keyboardVisible focus and reachable controlsDevice 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.

Try the method on a bounded example

Write a test for the enquiry submission button. Start on an identified service page in the preview version. Enter a fictional name, an agreed test address and a recognisable test message. Expect accurate browser feedback and a message the recipient can locate in the agreed receiving system. If only the confirmation appears, the test is incomplete. Record receipt as unverified rather than passed. This simple distinction exposes a journey that looks complete while actual delivery remains unproven.

Questions, answered

Is a Lighthouse run an acceptance test?

It can contribute technical evidence, but does not check the full commissioned scope, customer journeys or your team’s ability to edit the site.

Can we test against the live website?

Prefer an isolated preview environment and fictional data. Tests affecting real users or external systems need their own plan.

IMBAHUB

What would you like to make possible?

An acceptance test compares the delivery with what you commissioned. Choose real tasks, state what should happen and record the outcome. An attractive homepage does not prove that an enquiry arrives or that your editor can make the next change.

Talk to us
Product interface set to English in an isolated environment with fictional English demo content.

Product interface set to English in an isolated environment with fictional English demo content.