UAT planning
Scope, timetable, roles and entry and exit criteria agreed up front.
User Acceptance Testing (UAT) Services
Prove the system works for the people who will use it, and agree it is ready, before you go live.
How we help
User acceptance testing is the last check before launch, and the one most often rushed. It is also where the business decides whether the system really does what it asked for.
We plan the UAT, write test scripts from your requirements, coordinate your users, record the results and keep a clear log of what passed, what failed and what is still open. You get a firm basis for the go-live decision.
- A confident go-live decision
- Requirements traced to test results
- Less strain on your own staff
- Evidence of what was tested and signed off
What is included
We agree the scope with you first, so there are no surprises.
Test scripts from requirements
Scenarios written in business language and traced back to what was asked for.
Coordinating your testers
Briefing and supporting the staff who do the testing, and keeping them on schedule.
Defect tracking and retesting
Logging issues, chasing fixes and retesting until they are closed.
Sign-off reporting
A clear summary of results to support your go-live decision.
Who we usually help
Not sure whether this is the right fit? Tell us about your situation and we will give you an honest view, even if that means pointing you elsewhere.
- Businesses implementing a new system
- Teams short on time to run UAT themselves
- Public and third-sector projects that need an audit trail
- Suppliers handing a system over to a client
How we work with you
-
01
Talk
You tell us what is eating up time or going wrong. We ask lots of questions and listen to the answers.
-
02
Agree
We write down what we will do, how often you will hear from us and what good looks like. Plain English, no jargon.
-
03
Get going
Your contact gets started and keeps you posted. We write down how everything is done so it is repeatable.
-
04
Improve
We check in regularly, fix what is not working and only suggest doing more when it will help.
Common questions
What is the difference between UAT and normal testing?
Normal testing checks the software works as built. UAT checks that it works for the business and the people using it, against the original requirements.
Do you need a requirements document?
It helps a great deal. If there is not one, we can work from user stories, process notes or by interviewing your team.
Can you run UAT for a system we bought rather than built?
Yes. UAT matters just as much for off-the-shelf and configured systems.
More from IT Services
Part of the same service, delivered by the same team. Here is what else sits alongside it.
Information Technology Services
IT advice, software testing, quality assurance and systems support from people who explain things in plain English.
Find out more
Software Testing Services
Hands-on functional, regression and exploratory testing that finds problems before your customers do.
Find out more
Quality Assurance Consultancy
Test strategies, QA processes and release checklists that help your team build quality in from the start.
Find out moreTell us what you need
Tell us what is going on. We will reply with an honest view and a clear proposal. No obligation, no pressure.
- Emailinfo@blakenbond.com
- Based inUnited Kingdom