Testing New Software Before Go-Live: 7 Steps for User Acceptance Testing
New software is often judged on the day it goes live. If staff cannot find a screen, a report shows the wrong totals, or a form rejects a perfectly valid CID number, confidence drops quickly, and it takes far longer to win back than it would have taken to catch the problem early. User acceptance testing (UAT) is the step where the people who will actually use a system check that it works for their real, everyday tasks before it is switched on for everyone.
Whether you are launching a new web application, a mobile app, an internal records system or an upgrade to an existing one, these seven steps help Bhutanese organisations test with purpose.
1. Agree what “ready” means
Before testing begins, write down what the system must do for you to accept it. Base this on the original brief or requirements: the key tasks, the reports management needs, and any rules the system must follow. A short, agreed list of acceptance criteria avoids arguments later about whether something is a defect or a new request.
2. Choose testers who do the work
The best testers are the staff who will use the system daily: the accounts assistant, the front-desk officer, the field supervisor. Include at least one person from each role, and give them protected time. Testing squeezed between other duties tends to be rushed and shallow.
3. Write simple test scenarios
Turn everyday work into step-by-step scenarios. For example: “Register a new applicant, upload a document, approve it, and print the letter.” Each scenario should state the expected result. Include the awkward cases too: long Dzongkhag and gewog names, missing fields, duplicate entries, cancelled transactions and month-end reports.
4. Test with realistic data in a safe copy
Use a separate test environment, not the live system. Fill it with realistic sample records so screens and reports behave as they will in practice. If you use copies of real records, limit who can access them and remove personal details where possible. Try the system on the devices and connections your staff really use, including older laptops, phones and slower internet links in district offices.
5. Record issues clearly
A note that says “it doesn’t work” is hard to fix. For each issue, record what you were doing, what you expected, what happened instead, and a screenshot if possible. Keep everything in one shared list or tracker, and give each issue a priority: must fix before go-live, should fix soon, or nice to have later.
6. Retest fixes, and check nothing else broke
When the development team reports a fix, the person who found the issue should confirm it. It also helps to rerun a few core scenarios after each round of changes, because a fix in one place can occasionally affect another. Plan for at least two rounds of testing rather than one.
7. Sign off and plan the go-live
When the agreed criteria are met and no “must fix” issues remain open, record a formal sign-off by the responsible manager. Then plan the switch-over: when it will happen, how existing data will be moved, who staff should call for help in the first weeks, and how you would roll back if something serious appears. Known minor issues can go into the support and maintenance plan.
Testing is part of the project, not an extra
Good testing does not need expensive tools. It needs clear criteria, the right people, honest feedback and enough time in the schedule. Building UAT into the project plan from the start makes go-live calmer for everyone and gives staff a system they already trust.
Talk to eDruk
Since 2004, eDruk Private Limited has developed software, web and mobile applications and ICT systems for organisations in Bhutan. If you are planning a new system and would like help preparing acceptance criteria, test scenarios or a go-live plan, or you would like us to build the solution with you, get in touch.
- Email: edruk@edruk.com.bt
- Phone: +975 2 332277
- Website: https://www.edruk.com.bt
