NGO ERP UAT Library
Acceptance tests need starting records, an action, a precise expected result and evidence from the delivered configuration.
Method And Expected Result
Attach environment, release, configuration and dataset versions. A partial result identifies the exact missing behaviour. Mandatory failures require resolution and retest before their scope is accepted.
Worked planning examples, not customer performance results. Changes stay in this page until exported; reloading resets them. Keep sensitive personal information out of this planning tool.
Working Sheet
| ID | Scenario | Expected result | Observed | Result | Evidence | Tester |
|---|---|---|---|---|---|---|
| UAT-01 | Budget 10000; actuals 6000; commitments 2000; request 3000 | Reject under test policy; available remains 2000 | Not tested | |||
| UAT-02 | Invoice 500 against existing commitment | Actuals 6500; commitments 1500; available 2000 | Not tested | |||
| UAT-03 | Replay settled donation event | One gift and posting; delivery retry logged | Not tested | |||
| UAT-04 | Revoke user access then export | Export denied under agreed revocation policy | Not tested | |||
| UAT-05 | Restore isolated backup | Balances, attachments and queue state reconcile | Not tested |
The Excel toolkit includes the UAT worksheet for this resource. CSV exports contain current values; Excel retains the calculator formulas.
