Sample report

A sample run report in the proposed format: run metadata, outcome counts, every check with expected and actual results, and the items that need a human decision.

Product preview. Sample data.

Each check ends in one or more assertions, statements of the expected result that the run compares against what the browser shows. The execution details list each step in the order it ran.

Run: run-2026-10-28-0412
Date: 2026-10-28 04:12 UTC
Environment: staging.example-shop.test
Trigger: scheduled
Browser: Chromium (sample)
Duration: 412s

12Passed

2Failed

1Skipped

Run summary as a table (sample data)
Outcome	Checks
Passed	12
Failed	2
Skipped	1
Total	15
Of which need review	2

Smoke checks

A smoke test is a short set of checks run first to decide whether a build is worth deeper testing.

Login with a valid account c-01 · 9sPassedExpected: Dashboard loads with the account name in the headerActual: Dashboard loaded; header shows "Sample User"Show execution detailsHide execution details
Sample screenshot
c-01 final state
Screenshot not included in this sample.
1. navigate /login
2. fill email
3. fill password
4. click Sign in
5. assert header text
Main pages reachable after login c-02 · 14sPassedExpected: Products, Orders and Settings return 200 and render their H1Actual: All three renderedShow execution detailsHide execution details
Sample screenshot
c-02 final state
Screenshot not included in this sample.
1. visit /products
2. /orders
3. /settings
4. assert h1 on each
Primary transaction: add one item to cart c-03 · 7sPassedExpected: Cart count increments to 1Actual: Cart count 1Show execution detailsHide execution details
Sample screenshot
c-03 final state
Screenshot not included in this sample.
1. click Add to cart on first product
2. assert cart badge = 1

Critical user journeys

Purchase from product page to confirmation c-04 · 48sFailed Needs reviewExpected: Confirmation page shows order number and totalActual: Step "Confirm order" timed out after 30s; confirmation page not reachedShow execution detailsHide execution details
Sample screenshot
c-04 at failure
Screenshot not included in this sample.
1. click Confirm order
2. wait for /orders/confirmation
3. timeout 30000ms
4. last network: POST /api/checkout 504
Requires review: Server returned 504 on checkout; could be environment, not application
Booking with date selection c-05 · 21sPassedExpected: Booking summary shows selected datesActual: Summary shows 12 Nov to 14 NovShow execution detailsHide execution details
Sample screenshot
c-05 final state
Screenshot not included in this sample.
1. open date picker
2. select 12 Nov
3. select 14 Nov
4. click Continue
5. assert summary text
Subscription renewal and plan change c-06 · 18sPassedExpected: Plan badge changes from Starter to TeamActual: Badge shows TeamShow execution detailsHide execution details
Sample screenshot
c-06 final state
Screenshot not included in this sample.
1. open /billing
2. click Change plan
3. choose Team
4. confirm
5. assert badge

Regression checks

Sign-up with email confirmation c-07 · 33sPassedExpected: Confirmation email link activates the accountActual: Account active; redirected to onboardingShow execution detailsHide execution details
Sample screenshot
c-07 final state
Screenshot not included in this sample.
1. fill sign-up form
2. read test inbox
3. open link
4. assert /onboarding
Account email change c-08 · 29sFailed Needs reviewExpected: New email shown in profile after confirmationActual: Profile still shows old email after confirmationShow execution detailsHide execution details
Sample screenshot
c-08 at failure
Screenshot not included in this sample.
1. open /settings/account
2. change email
3. confirm via test inbox
4. reload
5. assert email field
Requires review: Behaviour change or stale cache; needs a human decision
Password change c-09 · 16sPassedExpected: Login works with the new passwordActual: Login succeededShow execution detailsHide execution details
Sample screenshot
c-09 final state
Screenshot not included in this sample.
1. change password
2. sign out
3. sign in with new password
4. assert dashboard
Checkout with saved payment method c-10 · 25sPassedExpected: Order placed without re-entering cardActual: Order placed; order number shownShow execution detailsHide execution details
Sample screenshot
c-10 final state
Screenshot not included in this sample.
1. add item
2. checkout
3. select saved card
4. confirm
5. assert order number
Order history lists the new order c-11 · 8sPassedExpected: Latest order appears firstActual: Latest order firstShow execution detailsHide execution details
Sample screenshot
c-11 final state
Screenshot not included in this sample.
1. open /orders
2. assert first row contains order number

SaaS account flows

Team invitation accepted c-12 · 27sPassedExpected: Invited user appears as MemberActual: Member listedShow execution detailsHide execution details
Sample screenshot
c-12 final state
Screenshot not included in this sample.
1. invite member
2. read test inbox
3. accept
4. assert team list
Role change Member to Admin c-13 · 12sPassedExpected: Admin menu visible for the userActual: Admin menu visibleShow execution detailsHide execution details
Sample screenshot
c-13 final state
Screenshot not included in this sample.
1. change role
2. sign in as user
3. assert Admin menu
Invoice download c-14 · 0sSkippedExpected: PDF download startsActual: Skipped: no invoice exists in the sample accountShow execution detailsHide execution details
Sample screenshot
c-14 final state
Screenshot not included in this sample.
1. precondition failed: invoices list empty
Card update c-15 · 19sPassedExpected: Last four digits update in billingActual: UpdatedShow execution detailsHide execution details
Sample screenshot
c-15 final state
Screenshot not included in this sample.
1. open /billing
2. update card with test number
3. assert last four

Items requiring review

Checks whose outcome needs a decision from the team before anyone treats them as a defect.

Needs review c-04
Purchase: 504 on checkout; confirm whether staging was healthy at 04:12 UTC before treating as a defect.
Needs review c-08
Account email change: profile shows old email after confirmation; decide whether this is a product change or a defect.

Product preview. Sample data.

What would you like to stop checking manually?

Tell us about your application and testing challenges. We'll follow up about early access and whether Testivra fits your needs.

Get early access