White-Label QA Gate (QA)
A checklist with 7 steps: Freeze the client's brand tokens before QA begins.
By InnovaAI ResearchPublished
What are the steps?
White-Label QA Gate (QA)
- 01
Freeze the client's brand tokens before QA begins
Pull the exact hex codes, font stacks, and component radii from the client's design system into a single reference file. Any dashboard that renders with a default theme fails the gate immediately.
- 02
Test the embed inside the client's actual application shell, not a standalone preview
Load the dashboard in the client's staging environment at their real viewport sizes. A dashboard that looks correct in isolation can break when the host app applies its own CSS resets or z-index layers.
- 03
Verify tenant isolation with a cross-account probe
Log in as Client A, then attempt to load a dashboard URL belonging to Client B. The request must return an authorization error, not a rendered chart. Multi-tenant security is the single highest-liability item in any embedded deployment.
- 04
Confirm every chart renders against the client's production data shape
Run each visualization against a live or production-mirrored dataset. Empty states, null values, and timezone offsets are the three most common causes of a dashboard that passes demo QA and fails on day one of the retainer.
- 05
Check AI and natural-language query outputs against a fixed question set
Ask the same ten business questions the client's team will ask in week one. If the natural-language layer returns a different number than the equivalent chart, the client will lose trust in both.
- 06
Measure load time on the client's slowest expected connection
Throttle to a realistic mobile or remote-office speed and record time-to-first-chart. Anything above three seconds needs data acceleration or query caching before handoff, because slow dashboards get abandoned and abandoned dashboards do not renew.
- 07
Document the customization boundary in writing and get client sign-off
List exactly which elements are templated and which are bespoke. Over-customization is the category's primary margin risk, and a signed boundary document is the only reliable defense when the client requests a new chart type three weeks into delivery.