Written in by More Playables production team
Playable Ad QA Checklist and Sample Receipt
A practical checklist for package, lifecycle, interaction, viewport, audio, CTA, privacy, and destination checks.
Production checklist; sample receipt is an illustration
Updated
A receipt identifies the object under test
Start with the creative ID, master or variant, source revision, build timestamp, checksum, package size, network/product, language, orientation, and test environments. Without that identity, a pass can be accidentally attached to different bytes.
Package checks
- Expected entry point and archive shape.
- All required assets present and no accidental source maps, debug tools, or development files.
- References resolve without relying on an unapproved origin.
- Measured package size compared with the dated target requirement.
- Static scan for unexpected endpoints, permissions, identifiers, or third-party code.
Behavior checks
- Initial load and lifecycle gate.
- First action, invalid input, feedback, progress, win and fail states, and restart where scoped.
- Touch target behavior, drag cancellation, multi-touch rejection, and rapid repeated input.
- Background/foreground or visibility behavior where the host can change state.
- End card, CTA timing, destination, and prevention of automatic redirect.
Viewport, orientation, and audio
Test only the combinations promised in scope, but name them precisely. Include representative small and large viewports, safe areas, host controls, keyboard or screen-reader behavior where applicable, and orientation changes if supported. Verify that audio follows user-action and lifecycle expectations and that the creative remains understandable when sound is unavailable.
Result vocabulary
Result | Meaning |
|---|---|
Pass | Observed behavior met the stated check in the named environment |
Fail | Observed behavior did not meet the check; include reproduction evidence |
Not tested | Environment, access, or scope did not permit the check |
Not applicable | The check does not apply to this agreed creative or destination |
Conditional | Pass depends on a named host, account, configuration, or unresolved assumption |
Illustrative receipt, not an actual test
Check | Environment | Illustrative result | Note |
|---|---|---|---|
Package entry point | Static inspection | Pass | index.html at required location |
Portrait first action | Local mobile harness | Pass | First drag changed state |
External network preview | Unavailable | Not tested | Requires account access |
Campaign performance | Outside QA | Not applicable | Measured by the buyer's campaign systems |
This sample demonstrates the record structure. It is not evidence that a More Playables deliverable or a network submission passed.
QA versus approval
Internal QA reports what was tested. The buyer approves creative decisions. The external network applies its current technical and policy review. Campaign performance is observed after trafficking. Keep those four decisions separate.
Download the checklist and sample receipt; duplicate them for every export rather than editing one shared pass record.
Sources
Put this into practice
- Editable QA checklist
Use the checklist per delivered export.
- Illustrative QA receipt
See pass, fail, not-tested, and limitation fields.
Make your next test playable
Turn a creative question into a scoped playable, variant set, and delivery plan.
Start a playable brief