Backend feature tests cover important contracts including Core/local access, branch scope, AppSheet order-trip flow, sheet backbone, OE dispatch, stock transfer, sales agents, refunds/deductions and lorry-crane summaries. Frontend tests cover permission helpers and several order, trip, refund, state/district, quotation and SSO behaviours.
For a change, run the narrow affected tests first, then the full backend suite and frontend check/test/build commands defined by the current package scripts. A build passing does not replace workflow testing for stock and finance changes.
After a release or recovery:
| Signal | Investigate when |
|---|---|
| API/application errors | Error rate rises or a critical action fails repeatedly |
| Database health | Connections, storage, locks or query latency approach limits |
| Sheet-sync outbox | Pending/failed count grows or retries repeat the same error |
| OE job log | Draft/commit jobs fail, duplicate or stop appearing |
| Stock discrepancies | Unexpected spikes or negative/overcommitted availability |
| Approval queues | Old payments/refunds/stock actions remain unattended |
| Authentication | Core callback/session failures or provisioning errors rise |
Capture user, time, environment, branch, URL/action, record ID, expected versus actual result and correlation/job ID. Do not collect passwords, tokens or unnecessary customer data. Check audit/history and integration logs before attempting a repair.
Use supported application actions for correction. Direct SQL requires an approved incident/change procedure, backup, peer review and a reconciliation record.
The repository does not establish the live backup provider, retention or restore drill. Before handover, record:
After restore, reconcile database state with external AppSheet/OE systems before reopening writes.