A bug found during development costs minutes to fix. The same bug found by a hospital’s billing desk on a Monday morning costs hours, and some of the client’s trust. That’s why testing isn’t the last step in our projects. It runs through every stage.
Whether a client decides to build or buy, the custom parts have to work first time for the people who use them every day. Here is the checklist our team follows before anything goes live.
1. Before a line of code: agree what “done” means
- Every requirement has written acceptance criteria the client has signed off
- Each user role (front desk, accountant, manager, parent, field officer) has its key tasks listed
- A test plan covers which tests run at which stage, and who signs off
Most of the challenges we covered in common application development lifecycle problems begin with unclear requirements. This step prevents them.
2. Functional testing
- Every feature does what its acceptance criteria say
- Wrong inputs are handled clearly: empty fields, wrong formats, duplicate entries
- Calculations are checked against hand-worked examples: fees, interest, taxes, discounts, room tariffs
- Reports match the underlying data to the rupee
3. Integration testing
Most business apps don’t stand alone. They send data to accounting, receive it from an ERP, or sync with a mobile app. We test every connection in both directions, including what happens when the other system is slow or unavailable. This matters most for clients running integrated systems, where one broken link affects every report.
4. Device and network testing
- Tested on real Android and iOS devices, including low-cost phones with limited memory, not only the latest models
- Tested on slow and unstable mobile networks, not just office Wi-Fi
- Offline behaviour checked: does the app save work and sync when the connection returns?
- Tested at different screen sizes and with regional-language text, which often breaks layouts
5. Performance testing
We test at the busiest moment the client will face, not an average day. That might be month-end billing, results day, a festival weekend at a hotel, or every field officer syncing collections at 6 pm. If the app slows down under that load, it isn’t ready.
6. Usability testing with real users
This is the step most vendors skip, and the one clients notice most. Before launch, we sit real users in front of the app and ask them to complete everyday tasks without help:
- Can a receptionist check in a guest in under two minutes?
- Can a parent find this month’s fee due on the first try?
- Can a teacher mark attendance for 40 students without scrolling back and forth?
We watch where people hesitate, then fix the design, not the user. This is especially important for school and college apps, where users range from tech-savvy students to first-time smartphone users. Our user experience design team leads this step.
We also check accessibility: readable text sizes, good contrast and support for screen readers. Accessibility matters to us beyond software, as our skill training work with visually impaired students shows.
7. Regression testing
Every fix can break something that used to work. Before each release, we rerun the core test set, with automated tests for the most-used flows. AI tools now speed up parts of this work, as we discussed in AI-powered code assistants, but a person still reviews every result.
8. User acceptance and go-live
- The client’s own team tests with their real data and signs off
- Rollout is in stages where possible: one branch, one department or one campus first
- A rollback plan is ready in case something unexpected happens
- The first weeks after launch are watched closely, and issues are fixed fast
The checklist at a glance
| Stage | What we check | Done when |
|---|---|---|
| Requirements | Acceptance criteria, user roles, test plan | Client signs off the criteria |
| Functional | Features, inputs, calculations, reports | Every criterion passes |
| Integration | Every data connection, both directions | Data matches across systems |
| Device and network | Real phones, slow networks, offline sync | Works on the client’s lowest-spec device |
| Performance | Peak-day load | No slowdown at the expected peak |
| Usability | Real users doing real tasks | Users finish key tasks without help |
| Regression | Core flows after every change | Full core test set passes |
| Acceptance | Client’s team, real data, staged rollout | Client signs off go-live |
Learn more about our software testing services, or see how we build web and business applications and mobile apps.
Have an app that needs testing, or one that needs building right the first time? Talk to Kwantify Solutions.
