Functional and manual
A person working through the software the way a customer would, including the things a customer does that nobody planned for.
5 products, each grown from client work.
Licensed, hosted and supported by the team that wrote them.
A person working through the software the way a customer would, including the things a customer does that nobody planned for.
Real Android and iOS handsets across screen sizes and OS versions, on a weak connection, because that is where most reports come from.
Endpoints checked for the failure cases — a timeout, a duplicate, a gateway that answers twice. The bugs that quietly corrupt data rather than showing an error.
What happens at month end, on sale day, when everyone arrives at once. Measured, with the bottleneck named, rather than guessed at.
Indicative figures while we settle the final rate card — tell us the brief and we will send a real number rather than a bracket.
Every number is a starting range, not a quote. What it actually costs comes back in writing after one call — with the scope it is attached to.
That is most of this work. We come in with no assumptions about how it is supposed to behave, which is usually an advantage.
No. Automation earns its cost on things that run every release; most of the rest is cheaper and better tested by a person. We will tell you which is which instead of selling you a suite.
A report of what was tested, what failed, what was fixed and re-checked, and what we did not cover. The last part matters as much as the first.
One reply from the person who would do the work.
Hello. Tell us what you are trying to build, or what is going wrong with what you have. A person reads these — not a bot.