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