Website change testing · 6/6 verified

Validate a website change against every acceptance criterion

A change validation can begin with “does that page load?” and extend through the complete business workflow. In this run, Mira verified six criteria from sign-in to order confirmation.

Recorded · Pass · 6/6 verified

Controlled Sauce Demo checkout. No real account, order, payment, or customer data was used.

The acceptance criteria

The definition of done travels with the run

“Validate the complete checkout journey. The change passes only when all six criteria are visibly satisfied:”

  1. 01 Sign in successfully
  2. 02 Product catalogue loads
  3. 03 Add a product to cart
  4. 04 Cart keeps the selection
  5. 05 Checkout accepts customer details
  6. 06 Order confirmation appears

One system, three levels of proof

Use the smallest test that answers the question

Level 1

Does the page load?

Open a URL and verify the important headline, form, or status is visible. Useful as a quick repeatable smoke test.

Level 2

Can the user finish?

Run the saved customer journey through its final form, booking, purchase, or confirmation. Repeat it manually or on a schedule.

Level 3

Did the change meet every criterion?

Track each acceptance criterion through one or more workflows and return a release decision with visible evidence.

Acceptance criteria testing

The answer becomes clearer as the workflow progresses

0/6

The page loaded, but nothing was validated yet.

3/6

The account and catalogue worked; checkout was still unproven.

6/6

The order confirmation completed the final acceptance criterion.

Acceptance criteria still in progress during website change validation
An intermediate page is not mistaken for a completed change.
All six criteria completed by the post-deployment validation
The final state shows all six criteria verified.

What this proves

A release decision can be tied to visible criteria

The recorded change validation tracks six separate outcomes and only reports success after the final order confirmation appears.

What it does not prove

One workflow covers every release risk

A real change may need several journeys, roles, viewports, and negative criteria. The validation is only as complete as the agreed definition of done.

Video description and transcript

The film opens with “Testing changes is tough. Let us do it.” A browser performs the Sauce Demo checkout while a panel tracks six acceptance criteria.

The criteria change from pending to verified as sign-in, catalogue, cart, customer details, and order confirmation complete. The final screen reads “Change validated.”

Give Mira your definition of done.

Get a pass you can defend or a specific workflow that still needs work.

Get early access See CMS testing