Sample delivery
One flow. From risk to a useful finding.
Follow PAY-01, a checkout-total scenario, through each part of the delivery. These are illustrative materials, not a real client report; the numbers are examples.
01 / RISK & PRIORITY
An incorrect checkout total affects trust.
Our example starts with no documented cases. Product review identifies 30 high-priority scenarios; PAY-01 checks that a discount is reflected in the checkout total.
- Priority
- High: payment-related customer journey
- Preconditions
- Client test user, test environment and a prepared cart with a discount applied
- Expected result
- The checkout total is $120.00
- Case identity
- PAY-01 is preserved across the plan, test and report
02 / IMPLEMENTATION
A test your team can read.
The custom wrapper provides page objects and prepared test data. Named steps connect the business scenario to its assertions. The example assumes the cart and discount are prepared by the fixture.
import { test, expect } from "../fixtures/test";
test("PAY-01: checkout charges the correct total", async ({ page, home }) => {
await test.step("Authenticate customer", async () => {
await home.login();
});
await test.step("Open and validate checkout", async () => {
await home.goToCheckout();
await expect(page.locator(home.HEADER)).toBeVisible();
});
await test.step("Verify the discounted total", async () => {
await expect(page.locator(home.TOTAL)).toHaveText("$120.00");
});
await test.step("Place the order", async () => {
await home.placeOrder();
});
await test.step("Verify order confirmation", async () => {
await expect(page.locator(home.CONFIRMATION)).toContainText(
"Order Confirmed"
);
});
});03 / EXECUTION & REPORT
30 executed. One result needs attention.
A scheduled or release-triggered pipeline executes the agreed suite and publishes results. In this illustrative run, 29 tests pass and PAY-01 fails because the displayed total is $135.00.
04 / HUMAN ANALYSIS
Keep the defect visible.
The example finding is a missing discount in the checkout calculation. The expected amount remains $120.00; changing the test to accept $135.00 would hide the problem.
- Severity
- High in this example: the displayed payment total is wrong.
- Evidence
- Expected $120.00; actual $135.00 in the prepared test scenario.
- Recommendation
- Review discount calculation before release, then rerun PAY-01.
- Responsibility
- Qalitative reports the finding. The product team reviews the code fix and release decision.
What if the product intentionally changes?
An intentional UI change is a different case. Review the new behavior, update the affected test, rerun it and submit the repair for review.
See the maintenance approachDefine your first step.
A free 30-minute conversation about your testing needs. A formal audit is a separate engagement.