Synthetic order: cross-layer verification
Order journey: REST, SOAP, browser, SQLite and UX · Execution evidence · 2026-11-02T19:37:17.608Z
Mapping coverage is not proof that a requirement is satisfied. Outcomes reflect the mapped cases and their explicit assertions; review acceptance criteria, untested business rules and open questions.
- Production business rules and performance budgets are outside this synthetic example
- Manual accessibility and usability review remains necessary
| Requirement & acceptance | Mapped test cases | Observed outcome |
|---|---|---|
ORDER-01 Create an order through REST
| order-e2e · Create an order, verify browser and database, then inspect UX | passed |
ORDER-02 Order ID, product and status match across API, browser and SQLite; unknown orders return documented 404 | order-e2e · Create an order, verify browser and database, then inspect UX order-not-found · Unknown order returns the documented negative response | passed |
SOAP-01 SOAP Add returns 5 for 2 and 3 without a fault | soap-add · SOAP addition uses an explicit XML result assertion | passed |
UX-01 No detected violations under the selected axe WCAG A/AA rules | order-e2e · Create an order, verify browser and database, then inspect UX | passed |
UX-02 No horizontal overflow at 390 by 844 CSS pixels | order-e2e · Create an order, verify browser and database, then inspect UX | passed |
PERF-01 API and query checks meet the illustrative local timing thresholds | order-e2e · Create an order, verify browser and database, then inspect UX | passed |