Stack hubs
QA by stack
The defaults that decide what a tester checks, read from each vendor's docs with dates, and the checklist items they map to.
Vercel
Release testing for Next.js apps
Server actions are endpoints, page checks do not protect them, and NEXT_PUBLIC_ variables reach the browser. The checklist tests the app the way a request does, not the way the UI does.
6 verified defaults
Supabase
Regression testing for Supabase backends
Row-level security is the authorization layer, and the publishable key in the browser is safe only because of it. A table without a policy, or with a permissive one, is the single most documented failure on this stack.
5 verified defaults
Google
Release testing for Firebase apps
Clients talk to the database directly and Security Rules are the only safeguard. Rules can be unit-tested in the emulator before they deploy; the checklist requires that they are.
4 verified defaults
Stripe
Release testing for Stripe integrations
Payments and plan state arrive as signed webhook events that can be duplicated and can arrive out of order. The checklist sends the events the docs warn about and checks the account state afterwards.
5 verified defaults
Meta
Release testing for React Native apps
The JavaScript bundle ships to the device, so anything in it is readable, and purchases only behave in the store sandboxes. Release builds differ from debug builds; the checklist tests the former.
5 verified defaults
Expo
Release testing for Expo apps
EAS Update ships JavaScript changes over the air without a store submission, and EXPO_PUBLIC_ variables are inlined into that bundle. Both are release surfaces the checklist treats as such.
4 verified defaults