Exploratory Testing

Find the bugs you didn’t think to test

Agent Description

Exploratory Testing is particularly useful for edge-case testing. It uses a "fuzzier" agent that is built in a way for it to be more “loose” in its trajectory and less deterministic to simulate actual non-linear end user behaviors.

This is especially useful in user flows like checkout, multi-step user journeys where most real issues are flagged in the non-linear journeys liked adding and removing items from cart or moving back and forward in the funnel

Core Agent Objectives

  • Test unpredictable user paths automatically
  • Locate the bugs that scripts can not
  • Boost coverage with new paths every run
Exploratory Test

Case Overview

Platform: Native Mobile App (Android)
Device: Pixel 4a
Android Version: 35
User Type: Tobacco Member
Test Result: Failed at step 5 - Points display configuration error

View the run-time bug
See Full Test
Exploratory Test

Case Overview

Platform: Web Browser
Website: Rockefeller Center
Test Type: E2E Purchase Flow

View the run-time bug
See Full Test
Exploratory Test

Case Overview

View the run-time bug
See Full Test
Exploratory Test

Case Overview

View the run-time bug
See Full Test
Exploratory Test

Case Overview

Revenue accuracy, pricing accuracy, discount validation, checkout conversion rate

View the run-time bug
See Full Test
Exploratory Test

Case Overview

View the run-time bug
See Full Test
Another test type

Case Overview

View the run-time bug
See Full Test

Bug Book

These are production bugs found for our actual customers

Explore Bugs Caught
Exploratory Testing

“Best Sellers” link in header leads to a 404 page

See Full Test
Exploratory Testing

Meal selection page stuck loading

See Full Test
Exploratory Testing

Rewards page shows incorrect annual redemption limit

See Full Test

Platform: Native Mobile App (Android)
Device: Pixel 4a
Android Version: 35
User Type: Tobacco Member
Test Result: Failed at step 5 - Points display configuration error

Exploratory Testing

Checkout button leads to error page

See Full Test

Checkout completion rate, conversion rate, revenue

Exploratory Testing

Reviews reference a different item (dress) on shorts page

See Full Test
  • Prevented over $400k in lost sales
  • Saved 21 hours in dev time on the bug
  • Automated 21 hours in dev time on the bug
Previous
Next
QA time per release dropped from four days to one

How OneSafe Cut Release QA From Four Days to One

Read Case Study

Schedule A Demo

We invite you to try us out with our new Pilot Program

Book A Demo