Kids app testing checklist

Download the checklistMarkdownCSVBrief (Markdown)

1. 1.release smoke testsDone when: On the release build, a child opens the app, plays the first activity, and any purchase or link asks for the parental gate.Risks: store-rejection. Tool class: mobile automation. Usually run by: QA engineer.
2. 2.end-to-end functional testsDone when: Every purchase, chat and outbound link asks for the parental gate, and chat is off on a new child profile until a parent turns it on.Risks: money-loss, user-harm. Tool class: mobile automation. Usually run by: QA engineer.
3. 3.exploratory testingDone when: A tester posing as an adult stranger cannot find, message or voice-chat a child profile, and a child cannot send their name or location in free text.Risks: user-harm. Tool class: test management. Usually run by: QA engineer.
4. 4.payment and money-flow testingDone when: In the store sandbox, each purchase asks for a fresh parent approval and produces one charge, and a second tap within a minute does not buy again.Risks: money-loss. Tool class: mobile automation. Usually run by: QA engineer.
5. 5.compliance checksDone when: A reviewer confirms the SDK list matches the store declarations, contains no third-party analytics or ad SDK outside the families-certified list, and the parent consent step comes before any personal data leaves the device.Risks: regulatory-penalty, store-rejection. Tool class: test management. Usually run by: product manager.
6. 6.analytics and event tracking testsDone when: A network capture from install through first play shows no advertising ID, location or device serial sent to any third-party domain.Risks: regulatory-penalty, data-breach. Tool class: proxy. Usually run by: QA engineer.
7. 7.security scanningDone when: The dependency report names every SDK in the build and flags none that requests location or contacts a domain outside the approved list.Risks: data-breach. Tool class: dependency scanner. Usually run by: security specialist.
8. 8.device and browser compatibilityDone when: The app installs and plays on each supported tablet and phone model and OS version, including shared family devices with parental controls on, and the parental gate appears before any purchase or link on each.Risks: store-rejection. Tool class: device cloud. Usually run by: QA engineer.