How testing works (read this first)¶
This page explains how to run any test plan on this site. Every plan (Billing, Payroll, Super, …) follows the same rules.
Test mode only — never use real money or a real ATO/Beam account
All testing happens in a test / staging environment. Never enter a real credit card, and never lodge to the real ATO or send a real super payment to Beam. Payroll and Super talk to the ATO and to the Beam clearing house — a wrong lodgement in production reports real money to the government or moves real super. If you are unsure whether you are on the test environment, stop and ask a developer.
How to run a plan¶
- Open the plan page. A Test-run panel appears at the top — fill in your name, the date, and the environment you are testing.
- Work through each test case in order. Every case has Steps, a ✅ Pass if result, and ❌ Fail if signs.
- In each case's result box, choose Pass, Fail, or Blocked, and add any notes / evidence (a bug reference, a screenshot filename, or what you saw).
- The summary at the top keeps a live tally (e.g. 18 pass · 2 fail · 4 not run).
- When finished, click Print / Save as PDF and keep the file as your evidence. Your entries are saved in your browser as you go, so a refresh won't lose them. Reset run clears the page for the next round.
Each tester saves their own PDF — results are not shared between testers or stored centrally.
How to read a test case¶
- Steps — do these in order.
- ✅ Pass if — what you should see. If you see this, mark the case Pass.
- ❌ Fail if — signs something is wrong. Mark Fail and log a bug.
- Blocked — use this when you couldn't run the case (e.g. a dependency isn't ready, or it needs a developer who wasn't available).
Severity — how serious is a failure?¶
| Severity | Meaning | Examples |
|---|---|---|
| 🔴 Blocker | Wrong money, wrong ATO/super report, or data loss. Must be fixed before release. | Wrong tax/super calculated; a pay run lodged to the wrong financial year; a super payment sent twice; an employee deleted who was in a pay run; one company seeing another's data. |
| 🟠 Major | A feature behaves incorrectly, but no money/compliance/data-safety problem. | A button does nothing; a validation message missing or wrong; a download fails; a status shown incorrectly. |
| 🟡 Minor | Cosmetic only. | A typo, misaligned layout, or a date shown as mm/dd/yyyy instead of dd/mm/yyyy. |
The 🔧 marker¶
Cases marked 🔧 Needs developer setup require a developer to trigger or simulate something for you — a failed renewal, a Beam notification, an ATO response, a background job. You still check the result yourself; just ask a developer to set it up first. These are common in Payroll (ATO responses) and Super (Beam clearing-house notifications), which can't be produced by clicking alone.
Australian formatting rule¶
Dates must display as dd/mm/yyyy everywhere (Australian locale). A date shown as mm/dd/yyyy is a 🟡 Minor bug — log it. Money is shown in AUD.
How to report a bug¶
Log every failure with: the case number; what you expected vs what happened; a screenshot; which account/company/employee you used; the severity; and the date/time + browser.