End-to-end QA for a children's healthy eating platform
Establishing a complete quality assurance process for Stir Crazy Kids, covering their web app, mobile ordering application, and multi-platform release readiness from the ground up.
Client
Stir Crazy Kids
Headquarters
Mornington Peninsula, Australia
Engagement
3 to 6 months, 1 QA engineer
Platforms
Web (Windows, Mac), Android, iOS
Technologies and tools
Jira
Google Sheets
Google MeetResults by the numbers
0→1
QA process built from scratch
4
Platforms and browsers covered
100%
Critical and blocker issues reported
Daily
Reporting and communication
✓
Structured regression before every release
✓
Test matrix across all devices and platforms
Here's a bit about Stir Crazy Kids
Industry
FoodTech
Offering
School lunch ordering
Region
Mornington Peninsula
Platforms
Web, Android, iOS
Stir Crazy Kids is an Australian platform dedicated to building healthy eating habits in children, through school canteen services, cooking classes and cooking parties across the Mornington Peninsula and surrounding areas. At the core of its digital offering is a web and mobile ordering application that lets parents order school lunches for their children in advance, across multiple students in a single transaction.
As the platform grew to serve multiple schools at once, the team needed a structured quality assurance function to keep the ordering experience reliable, accessible and consistent across the devices and browsers used by its parent and school communities. With no QA process in place, Stir Crazy Kids brought QAble in to build one from the ground up.
Before and after QAble
Before QAble
With QAble
No QA process in place
No structured test cases or test design documentation
No cross-browser or cross-platform validation
No regression testing before releases
No formal bug tracking or defect reporting process
No visibility into product quality for stakeholders
Critical and blocker issues going undetected pre-release
No daily or weekly quality reporting to stakeholders
No structured workflow for reviewing development tickets
Our engagement
Our QA engineer joined the Stir Crazy Kids team with a clear mandate: build a reliable quality assurance function from scratch. With no prior testing process in place, the engagement began by establishing the foundations, designing test cases across all key user journeys, setting up a structured test matrix spanning Windows/Chrome, Mac/Safari, Android and iOS, and introducing Jira as the central hub for bug tracking and task review.
Testing ran across the full lifecycle of each release. Smoke testing validated baseline stability at the start of every cycle, while exploratory testing surfaced unexpected edge cases across the ordering flow, menu management and multi-student checkout experience. A rigorous regression suite ran before each release to give a clear go/no-go signal, giving the team confidence that critical and blocker-level issues were identified and resolved before reaching users.
Throughout the engagement, our QA engineer maintained daily and weekly quality reports, keeping the Stir Crazy Kids team fully informed on test progress, open defects and release readiness. Communication over Slack and Google Meet kept the team tightly aligned with development, enabling fast triage of high-priority issues and smooth coordination through every sprint cycle.
Engagement highlights
A QA process built from zero: structured regression before every release, a full device and platform test matrix, and 100% of critical and blocker issues reported before launch.
Engagement type
3 to 6 months
Team size
1 dedicated QA engineer
Platforms covered
4 (desktop and mobile)
Outcome
100% critical issues reported
What QAble delivered
Services
Functional and UI testing
Our QA engineer designed and maintained structured test cases covering all critical user journeys, including lunch ordering, menu browsing, multi-student checkout and account management. Test cases were documented in Google Sheets with a detailed test matrix mapped to each device and platform. Ongoing test case maintenance kept coverage current as the platform evolved, with Jira used to review developer tickets and validate fixes against acceptance criteria.
Give every release the quality process it deserves, from day one
Talk to us about building a QA process for your platform, from test design to daily reporting and release signoff.
QA built for platforms families trust every day
Family-facing platforms can't afford undetected bugs. QAble brings structured regression, cross-platform coverage and daily visibility to every release.
Talk to QA Advisor
Direct access to QAble's QA specialists. No pitch, just answers.
Response within 24 hours