1. Automated validation
- Run
npm.cmd test. - Regenerate the workflow manual.
- Smoke-test all indexed pages.
- Confirm zero validation warnings.
50workflow procedures
50indexed screens
14document outputs and worksheets
5role journeys
Release gates
No release until each gate is signed off.
2. Individual estate journey
- Register a synthetic user.
- Complete profile, assets, liabilities, dependants and beneficiaries.
- Recalculate estate and verify liquidity/duty outputs.
- Generate family and calculation reports.
3. Document autofill
- Open date-of-death autofill readiness.
- Confirm death notice, next-of-kin, asset inventory, administration letter, executor acceptance, tax, distribution, voucher and executor-certificate worksheets map correctly.
- Generate the pack using synthetic data only.
4. Collaboration journeys
- Test family profile creation and invite acceptance.
- Test professional profile, client invite, risk inbox and review queue.
- Test vault share, revoke and shared-file access.
- Test executor mode and task seeding.
5. Security boundaries
- Unauthenticated users must be blocked.
- Non-admin users must not open admin tools.
- User A must not access User B estate.
- Generated files must remain UID/estate scoped.
6. Deployment proof
- Deploy Hosting, Realtime Database rules and Storage rules to the intended Firebase project.
- Open live
firebase-config.jsand confirm project ID. - Run one synthetic end-to-end journey on the hosted URL.
Role journeys
Test by user type, not by page list.
A release is only useful if each user can complete their real job. The PDF manual expands every item into detailed procedure steps.
Individual / estate ownerCapture estate data, model tax/liquidity/distribution, generate reports and document packs.
Family coordinatorCreate separate family member profiles, invite people, review emergency readiness and reports.
ProfessionalCreate firm profile, invite clients with consent, triage risk, review estate data and manage billing/settings.
Executor / administratorActivate executor mode, seed tasks, prepare Master/SARS/voucher worksheets and track cases.
Program owner / adminRun CRM, payments, invoices, support, reviews, plan builder, diagnostics and launch checks.
Autofill coverage
Document workflows that must be tested with synthetic data.
| Output | Source data to verify | Pass condition |
|---|---|---|
| Notice of death details | Identity, date of death, marital status, address and estate reference | Every required field is mapped or listed as missing. |
| Next-of-kin details | Spouse, beneficiaries, dependants and trusted contacts | Family records are listed without duplicates. |
| Executor asset inventory | Immovable property, assets, ownership and values | Asset inventory matches the estate data. |
| Master reporting letter | Administration office, executor, estate reference and annexures | Cover-letter worksheet and annexure index are present. |
| Executor acceptance / authority | executor acceptance fields, executor firm, agent and scope notes | Authority worksheet is clearly marked for professional review. |
| estate-duty return and SARS | Tax number, duty values, dutiable estate and SARS status | Tax workflow identifies missing official references. |
| L and D account / vouchers | Assets, liabilities, beneficiaries, distribution and checklist | Unbalanced distribution or missing vouchers are visible. |
Privacy rule: test and generated evidence must use synthetic names, synthetic ID numbers and harmless dummy files. Do not use real client documents for QA.
Operator runbook
Regenerate the procedure PDF after workflow changes, run validation, test all indexed pages, then complete one end-to-end synthetic journey for each role before any demo or release.
npm.cmd test
python scripts/build-workflow-qa-manual.py
npx --yes firebase-tools@latest deploy --project estateflow-7df62 --only hosting,database,storage