All case studies

Testing the product the way real people use it

For about six months, we acted as the only QA resource for an event platform. We tested the software as organisers and attendees would.

How it works

  1. 01Human decision

    Real journeys

    Test as an organiser and attendee would, including edge cases.

  2. 02

    Log issues

    Log steps to reproduce, screenshots, severity, and impact.

  3. 03Human decision

    Triage issues

    Agree priority with developers. Critical issues are handled the same day.

  4. 04

    Fix

    The development team fixes the issue.

  5. 05Human decision

    Retest

    Check the fix before and after release.

The problem

The event platform was approaching its first live events while adding new features. They needed quality assurance. We stepped in as their only QA resource for about six months. We tested the software the way real people use it.

Our approach

We tested the platform as organisers and attendees. Every issue was logged with steps to reproduce, expected and actual behaviour, screenshots, severity, and impact. Once the development team applied a fix, we retested it to make sure it worked properly.

What we built

We tested registration, waitlists, payments, refunds, check-in, team assignments, and AI-written content. We also tested large events with over 100 attendees. We caught serious issues, like a payment that went through while showing an error, overbooking when groups did not fit the remaining places, export mismatches, and slow pages.

The results

  • Tested payments, registration, large events and AI content over about six months.
  • Caught serious issues, like a payment succeeding while showing an error.
  • Every fix was retested before and after release.

All figures come from our own project records and are not independently audited.

Next storyA forecasting product, from first data to launch-ready code

Sound familiar? Try the scorecard or book a call.