CONTROLLED SYNTHETIC FIXTURE

A finding you can inspect.

Reproduction steps, an observed result and the scope left untested. This is how a useful QA finding starts.

ESTECH · Run · Reviewed

Synthetic sample — not customer work. This intentionally broken local test store uses synthetic data and simulated payments. No real payment was processed. The reviewed, checked-in Playwright demo suite executed the checks; this summary was prepared from the saved report and inspected artifacts.

Discount lost after a payment retry

Review required. The expected final total was €80; the observed total was €100 on both execution attempts.

Finding CHECKOUT-001 · Owned local fixture · Executed 28 October 2026.

Suggested priority: High in this example. The displayed total loses the agreed discount after a successful payment retry. No real payment or customer impact occurred.

Reproduction steps

  1. Add the €100 headphones to the controlled store’s cart.
  2. Apply coupon SAVE20; confirm the displayed total is €80.
  3. Select the simulated declined test-card action; confirm “Payment declined.”
  4. Select the simulated valid-card retry action; confirm “Payment successful.”
  5. Check that the discounted total remains €80.

Observed: the final total was €100. Both execution attempts failed the final €80 assertion. The payment retry above is part of the journey; the automated test retry reran the entire check once. The fixture is deliberately broken; root cause was not autonomously established.

Controlled test store after simulated payment retry: SAVE20 is entered, one item is in the cart, Payment successful is shown, and the total is €100 rather than the expected €80.
Screenshot from the first failed attempt. The second attempt also observed €100 instead of €80. Open full-size evidence.

The saved report classifies this as suspected_product_defect. Repeated assertion failure is observed evidence; that label does not establish an automatically verified root cause.

Scenario results and untested scope

ScenarioRecorded outcomeDecision
Healthy fixture4 passed, 0 failedCHECKS PASSED
Deliberate checkout defect3 passed, 1 failedREVIEW REQUIRED
Fixture unavailable before execution0 executed, 4 blockedINCOMPLETE
Fixture identity changed after run4 passed, identity mismatchINCOMPLETE
Fixture identity unavailable after run4 passed, identity unreachableINCOMPLETE

Every plan selected the same four checks: storefront availability, the initial €80 coupon total, discount survival after payment retry, and the quote API response. Account settings was excluded from the five-check catalog. The unavailable scenario started no browser or test attempts. In the deliberate-defect scenario, three passed and one failed. In the final two scenarios, all four selected checks passed, yet the overall decision remained INCOMPLETE because post-execution environment verification failed. Passing assertions alone cannot establish a complete trustworthy run when the fixture identity cannot be confirmed unchanged.

What the evidence establishes

Each failed attempt retained a screenshot, trace, browser log and error context. Passing checks retained appropriate logs and API observations, including the quote API response confirming €80. Raw artifacts contain private paths and are not published; only this synthetic screenshot and report summary are public.

Agree your first QA scope

ESTECH offers a fixed-price one-time QA review (EUR 500 / US$570) and an optional four-week senior-led service from EUR 2,500 / US$2,850. Sentinel remains a controlled demo. Final scope, taxes and terms are agreed in writing.

Request a QA review

Or email support@estechsentinel.com. Please send a product overview, not credentials or customer data.