Business software · 6 min read
Why your developer shouldn't be the one testing their own work
A plain-English user acceptance testing checklist so real users catch problems before launch.
The short answer
User acceptance testing (UAT) is where real end users try a new system against real-world tasks before it goes live, to confirm it actually works for them, not just that it technically functions. A good UAT checklist covers realistic scenarios, edge cases, permissions and a clear way to log and fix problems before launch.
By Raja Wahab, Co-founder, Fixby Studios · Published · Updated · 6 min read
What user acceptance testing actually checks
Developers test that code works as written; user acceptance testing checks that the system works for the people who'll actually use it. A feature can be technically correct and still fail UAT if it's confusing, slow, or doesn't match how staff actually work.
User acceptance testing checklist
- Pick testers who represent real users, not just the project owner.
- Write test scenarios from real tasks: 'book a job', not 'click the booking button'.
- Include deliberate mistakes: wrong input, missing fields, cancelled actions.
- Check permissions: can a user only see and do what they're meant to?
- Test on the devices and browsers staff or customers actually use.
- Log every issue with steps to reproduce it, not just a vague description.
- Agree in advance which issues block launch and which can wait.
Developer tests their own code
- — Checks it works as written
- — Tends to miss real-world mistakes
Real users run UAT
- — Tests confusing or slow steps
- — Includes deliberate mistakes
A simple scoring approach
| Scenario | Expected result | Pass/Fail |
|---|---|---|
| Staff member creates a new job | Job appears in the correct status with correct details | Pass |
| Customer tries to view another customer's order | Access denied | Fail — flagged and fixed before launch |
| Form submitted with a missing required field | Clear error shown, no data lost | Pass |
“Use real staff doing real tasks, not just the developer checking their own work.”
Who should be involved
Include at least one tester who wasn't involved in building the brief. They're more likely to use the system the way a new starter would, surfacing confusing steps that the project team has stopped noticing.
Before you sign off
Don't sign off UAT just because testing happened; sign off because the agreed pass criteria were met and outstanding issues are genuinely minor. A rushed sign-off under deadline pressure is one of the most common causes of post-launch problems.
Common user acceptance testing mistakes
The most common mistake is only testing the ideal path through a system, which rarely reflects how people really use it. Another is letting the developer who built the feature also be the only person who tests it, since they tend to test what they expect to work, not what might go wrong.
A third mistake is treating UAT as a formality after the real decision to launch has already been made. Build in enough time to genuinely act on what testing finds.
Sources
Your questions
- What is user acceptance testing?
- It's the stage where real end users try a new system against realistic tasks before launch, to confirm it works for them in practice, not just that the code runs correctly.
- Who should carry out user acceptance testing?
- The people who'll actually use the system day to day, including at least one person who wasn't closely involved in writing the original brief.
- How long should UAT take?
- It depends on system size, but even a small project benefits from a few days of focused testing against real scenarios before going live.
- What happens if UAT finds a major issue?
- Fix and retest before launch if it affects core tasks or data security. Minor cosmetic issues can often be scheduled for after go-live if agreed in advance.
Raja Wahab is co-founder of Fixby Studios, a Huddersfield studio building websites, SEO, social media and business software for small, owner-managed businesses across West Yorkshire.
Next step
Let's get your business seen.
A free plan to replace spreadsheets and WhatsApp with one system.
Tell us which task takes too much time and we'll assess a focused software or automation project. Business automation and software
Prefer to talk it through? Contact Fixby Studios, email info@fixbystudios.co.uk or call 07737 067552.
