Client Portal Acceptance Test (QA)
A checklist with 8 steps: Freeze the build and record the platform version before testing starts.
By InnovaAI ResearchPublished
What are the steps?
Client Portal Acceptance Test (QA)
- 01
Freeze the build and record the platform version before testing starts
Note the workspace plan tier and any pending platform release notes, since a mid-test upgrade can change form behavior or record limits and invalidate your results.
- 02
Walk the primary client journey end to end on a real mobile device
Submit a live record through every form, trigger each notification, and confirm the confirmation state renders. Desktop-only testing misses the layout breaks that generate the first support ticket.
- 03
Verify role permissions by logging in as each user type the client named
A portal built in Noloco or Glide can look correct to an admin and still expose another client's records to a contractor role. Test with the lowest-privilege account first.
- 04
Confirm record limits and row counts against the contracted volume
Load the client's actual data, not a 20-row sample. Platforms priced per record or per workflow run behave differently at 50,000 rows, and the gap surfaces after go-live if you skip this.
- 05
Test every external integration with a forced failure
Disconnect the API key or revoke the OAuth token and observe what the user sees. Silent failures in a Bubble or Airtable sync are the most common source of disputed invoices.
- 06
Run the accessibility pass on forms, tables, and navigation
Check keyboard tab order, label association on inputs, and contrast on status badges. Client procurement teams increasingly require a documented result before signing off.
- 07
Log each defect with a reproduction path and a severity rating
Separate blockers from cosmetic items so the client can decide what ships now. An unranked bug list turns a two-day fix into a two-week negotiation.
- 08
Get written acceptance against the original scope document
List what was tested, what passed, and what was deferred. This signature is what protects the retainer when the client requests changes in month two.