Australia version. Set to Australia: prompts generate Australian test data (postcodes by state, +61 numbers, A$ with GST, ABNs that pass or fail the modulus 89 check) and keep TFNs and production data out. US version
AI Prompts for QA Engineers (Australia)
Prompt templates for Australian QA teams: test cases, bug reports, automation skeletons and Australian test data with postcodes by state and ABN check-digit cases.
The interactive tool loads here when JavaScript runs.
About this toolWhat is AI Prompts for QA Engineers?
With the region set to Australia, every prompt asks for Australian spelling in user-facing text, DD/MM/YYYY dates, A$ amounts with GST as the product specifies, 4-digit postcodes with state abbreviations and +61 numbers. It forbids real identifiers: no real TFN, Medicare number or another business's ABN in a fixture.
Australian validation logic often uses a published algorithm, and the prompts make the model test both sides of it. The ABN check on the Australian Business Register subtracts 1 from the first digit, weights the 11 digits (10, 1, 3, 5, 7 and so on to 19) and requires the total to divide by 89. The synthetic data template asks for ABN-format values labelled as passing or failing that check, postcodes that match their state (including NT postcodes with a leading zero, which break integer fields) and unit addresses written as "4/120 Main St".
Accessibility tests target WCAG 2.2 level AA unless the team has agreed another level; the Disability Discrimination Act 1992 applies to websites and apps as it does to other services.
- Ten QA templates from test design and bug reports to flaky-test triage and release readiness
- Framework choice for Playwright, Cypress or Selenium skeletons
- Boundary value and equivalence class instructions built into test-case prompts
- Flags emails, phones, card-like numbers and IP addresses in pasted logs
- Favourites, keyword search and a Markdown library export for your QA wiki
Updated
How to use AI Prompts for QA Engineers
- Name your product and team context, for example B2B billing web app, and pick a region if formats like dates or postcodes matter.
- Choose a template: Test cases from a user story, Bug report, Automation skeleton, Exploratory charter, Regression scope and more.
- Paste the story, acceptance criteria, notes or diff summary and set options such as the framework or priority scheme.
- Run the privacy check on logs or data you pasted, then copy the prompt into your assistant or IDE chat.
- Review the output: run the code, prune duplicate cases and confirm expected results with the product owner.
Worked examples
ABN validation cases
Input
Test cases from a user story, region Australia, story: "As a supplier I enter my ABN on the sign-up form"
Output
Cases for a valid ABN (51 824 753 556, the ABR's own worked example), the same number with the last digit changed (51 824 753 557, fails the check), spaces versus no spaces, 10 and 12 digits, and letters
The ABR's worked example sums to 534, which divides by 89 exactly. Changing the last digit breaks the sum, so 51 824 753 557 is a safe failing fixture that cannot belong to anyone.
Australian postcodes in synthetic data
Input
Synthetic test data set, region Australia, 20 customer rows in CSV
Output
Rows with postcodes matched to states (2000 NSW, 3000 VIC, 4000 QLD, 6000 WA, 0800 NT), +61 mobiles, A$ amounts and unit addresses, with edge cases labelled
The 0800 Darwin postcode loses its leading zero in any column typed as a number, a defect that only shows up with Northern Territory data.
Background and insight
Boundary value analysis and equivalence partitioning are decades-old test design techniques that models apply well when asked explicitly. If a field accepts 1 to 100 items, the interesting inputs are 0, 1, 2, 99, 100 and 101, plus invalid types. Without that instruction, a model tends to produce happy-path cases. The templates ask for the partition table first, then cases derived from it, so you can see whether a class was missed.
Generated test code is a skeleton, not a suite. A model cannot see your DOM, API contract or fixtures, so it invents selectors and endpoints. The Playwright, Cypress and Selenium template asks for user-facing locators (role, label or text) or test ids rather than CSS chains, explicit TODO comments for anything unknown, and no hard-coded waits, which are a common source of flaky tests.
Test data and logs often contain production customer data. Do not paste real records into a public assistant; under GDPR, data that can still be linked to a person remains personal data even when pseudonymised (Recital 26). The synthetic data template generates fictional records from a schema instead, and the privacy check flags emails, phone numbers, card-like numbers and IP addresses in anything you paste.
Common use cases
Sprint test design
Turn user stories and acceptance criteria into partitioned test cases with boundaries before the build lands.
Clear defect reports
Convert rough notes into reproducible bug reports with severity, environment and evidence sections.
Automation starts
Get a Playwright, Cypress or Selenium skeleton with page objects and TODOs to wire to your app.
Release decisions
Summarise test results, open defects and risks into a release readiness note for the go or no-go meeting.
Tips and limitations
- Store postcodes as text, then test with 0800 to prove it.
- Test GST rounding on line items and totals separately; per-line and per-invoice rounding give different cents.
- Never paste a TFN, even a colleague's, into a ticket or an AI tool; TFNs have their own legal protection.
Sources and further reading
- Format of the ABN, Australian Business Register
- Disability Discrimination Act 1992, Federal Register of Legislation
- Daylight saving, NSW Government
Frequently asked questions
How does the ABN check digit work?
Subtract 1 from the first digit, multiply each of the 11 digits by its weight (10, 1, 3, 5, 7, 9, 11, 13, 15, 17, 19), add the results and divide by 89. A valid ABN leaves no remainder. The Australian Business Register publishes the steps with 51 824 753 556 as the example.
Which accessibility level should Australian sites test to?
WCAG 2.2 level AA is the usual target, and government services follow the Digital Service Standard. The Disability Discrimination Act 1992 makes inaccessible services a discrimination risk for any organisation.
Can I use a real TFN to test a form?
No. TFNs are protected by tax law and the Privacy (Tax File Number) Rule, and should never appear in test data, tickets or AI prompts. Generate clearly fictional values and label them.
Can I paste production logs into an AI assistant?
Not with personal information in them unless your organisation has approved the tool. The Privacy Act 1988 applies, including the notifiable data breaches scheme. Mask logs here first; the check catches emails, phones, IP addresses, cards and labelled TFNs.
Will the tests cover Australian time zones?
If the product schedules anything, ask for it in the charter: Queensland, WA and the NT do not use daylight saving, and Adelaide and Darwin are half an hour off the eastern states, which catches code that assumes whole-hour zones.
Is there an in-depth guide to AI Prompts for QA Engineers?
Yes. “AI for Civil and QA Engineers: Prompts That Respect the Engineer of Record” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.