Verify testing
Every release, tested as every user before anyone sees it.
Before a release reaches your users, Appbricx tests it the way a careful tester would. It signs in as each kind of user, tries what they should and shouldn't be able to do, and opens every page in a real browser. A deploy refuses to go out while anything is red.
Static
- Contract is valid
- Every page is reachable
- Screens typecheck
Data
- Signed in as patient, doctor and front desk
- Each role reads and writes only what the contract allows
- Anonymous visitors can't read private tables
- Workflows armed and a backup exists
Browser
- Patient: every page opened and screenshotted
- Doctor: every page opened and screenshotted
- Front desk: every page opened and screenshotted
- Three stages
- Static, data and browser
- Role × table matrix
- Read, create, update, delete
- Real browser
- Every page, every role, screenshotted
- Skipped is not pass
- An unverified release says so
The three stages of verify
Static: the contract is valid, every page is reachable from some role's navigation, and the generated code and your components type-check.
Data: each demo sign-in works, every role is tried against every table for read, create, update and delete (writes rolled back), signed-out visitors can't read private tables, workflows are armed and a backup exists.
Browser: headless Chromium signs in as each role and opens every page it can reach, checking for errors and saving screenshots your agent can look at.
$ appbricx verify
static ✓ contract 4 tables, 2 roles, 8 pages, 4 workflows
✓ reachability, ✓ typecheck
data ✓ logins 3 demo logins (instructor, member)
✓ role-matrix 2 roles × 4 tables match the plan
✓ anonymous can't read the 2 private tables
✓ workflows 4 armed
browser ✓ walk:instructor 6 pages, no errors
✓ walk:member 2 pages, no errors
✓ nav-scope every role sees only its own pages
Tests your agent doesn't have to write
Permission matrix
Every role against every table for every operation, compared with what the contract says, on the real database.
Anonymous check
Lists which tables signed-out visitors can read, so private data never ships public by mistake.
Browser walk
Signs in as each role in headless Chromium and opens every page, catching errors a type-check can't.
Screenshots
The screenshot tool returns every page as each role, so your agent sees its own work and fixes it.
Gates deploys
appbricx deploy runs verify first and refuses on red. The CLI exits with code 1 for CI.
Fixes, not just failures
Every failing check names the role, table or page, with evidence and a suggested fix.
Eventra, verified as attendee, organizer and door
Each showcase app passes verify for every one of its roles. Eventra's report signs in as an attendee, an organizer and the door scanner, and its rules refuse a sold-out ticket and a second check-in.
Works with
Verify testing: common questions
What does verify test?
Three stages: static checks (contract, reachability, type-check), data checks (sign-in per role, a role by table permission matrix, signed-out access, workflows armed, a backup exists) and a browser walk of every page as every role.
Do I have to write the tests?
No. Verify derives every check from the contract: the roles, tables, pages and workflows you already described.
Can I run verify in CI?
Yes. appbricx verify exits with code 1 when anything is red, and appbricx deploy runs verify first and refuses to deploy on red.
What if a check is skipped?
Skipped never counts as a pass. A skipped stage means the release is unverified, and the report says so.