testivra
Get early access
Menu
Get early access

Critical user journeys

Give your most important workflows a repeatable check.

A handful of journeys carry most of a product's revenue or activation. They deserve a check that runs the same way every time and shows exactly where it stopped.

Get early accessView sample report

A critical user journey is a workflow that carries revenue or activation, such as checkout or sign-up.

Example scenarios

  • Purchase from product page to confirmation
  • Booking with date selection and confirmation
  • Subscription renewal and plan change

Proposed workflow

Each step names the capability it relies on and that capability's current stage. Steps that rely on a Planned capability describe intended use.

  1. Turn user journeys into tests Planned

    Write each critical journey as a scenario with the outcome that matters to the business.

  2. Run checks consistently Planned

    Run the critical set on a schedule against staging, and on demand before a release.

  3. Investigate failures with context Planned

    When a journey fails, see the step, screenshot and details together and mark items for review.

Sample output

Checks from the sample report that match this use case. Open a check to see its execution details.

  • 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
    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
    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
    Screenshot not included in this sample.
    1. open /billing
    2. click Change plan
    3. choose Team
    4. confirm
    5. assert badge
Product preview. Sample data.

Open the full sample report

Limitations

  • Defining which journeys are critical is the team's decision
  • Third-party steps (payment provider pages) may need test modes provided by the team

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