Testers who know the domain
We have built banking, payments, ERP and identity systems in East Africa since 2017. Our engineers know what a reversal, a late callback or a failed eTIMS submission looks like, so they test for it.
Software testing and QA services in Kenya for banking, payments and ERP
Manual and automated testing of the systems your money and operations run on: web, API and mobile apps, integrations, ERP rollouts and payment flows. Delivered as a project or as a managed QA team.
What this practice covers
Manual testing that finds real defects
Test cases written from your requirements and business rules, exploratory testing around them, and defect reports your developers can reproduce on the first read.
Automation that keeps up
Automated regression suites for web, API and mobile, run in your pipeline on every change, so a release no longer waits for a week of manual re-testing.
Performance before your customers find it
Load and stress tests on your APIs and apps at the volumes you expect on salary day, month end or a promotion, with the bottlenecks written up in plain language.
UAT your business can sign off
We prepare UAT scripts and data, guide your business users through them and track every finding to a decision, so sign-off means something.
The service in this practice
Test Automation
Automated regression suites for web apps, APIs and mobile apps, run in your CI pipeline on every change and handed over to your own team.
How we can work together
QA for a project
A test strategy, test cases, manual and automated testing and a release recommendation for one system, upgrade or integration, scoped after discovery.
Managed QA team
A monthly QA retainer: testers who learn your systems and test every release, with regression automation that grows over time.
Test automation set-up
A regression suite for your web app, APIs or mobile app, wired into your CI pipeline and handed over to your own team.
Why releases go wrong
Most production incidents are not exotic. A payment callback arrives twice. A rounding rule differs between the ERP and the bank file. A new screen works on the developer’s laptop and fails on a three-year-old Android phone on a slow network. Each one could have been caught by a test that nobody had time to write.
Testing is usually the step that gets squeezed when a deadline moves. We make it a planned, measured part of delivery instead.
What we test
- Web, API and mobile applications. Functional, regression and exploratory testing, on the browsers and devices your customers actually use.
- Banking and payments. Transfers, reversals, limits, fees and statements, and mobile money flows such as M-Pesa, Airtel Money and MTN MoMo, including timeouts, duplicate callbacks and reconciliation against bank statements or banks’ open APIs.
- ERP rollouts and upgrades. Odoo and other ERPs, tested against your real processes: invoicing, KRA eTIMS, stock, payroll and month-end close.
- Integrations. APIs, gateways and message flows between systems, including the failure cases: expired tokens, throttled callers and back ends that time out. See Integrations for the integration work itself.
- Performance and load. How your APIs and apps behave at peak volumes, and where they slow down first.
- User acceptance testing. Scripts, test data and support for your business users, with a clear record of what passed, what failed and what was accepted.
Manual and automated, together
Automation is not a replacement for people. Manual and exploratory testing finds the defects nobody thought to script. Automation makes sure that once a defect is fixed, it stays fixed. We use both: testers explore new features, and the regression suite covers what already works, running in your CI pipeline on every change.
We write automated tests with open-source tools your own developers can read and maintain, and we hand the suite over with the documentation to run it.
Projects or a managed QA team
Some organisations need testing for one release: a core banking upgrade, an ERP go-live or a new integration. Others ship every week and need testers who already know their systems. We do both. A project starts with a test strategy and ends with a release recommendation. A managed QA retainer gives you a team that tests every release and grows your regression suite month by month.
Testing and security
Functional testing tells you a system does what it should. Security testing tells you it does not do what it should not. When a system handles money or personal data, we plan both together with our Cybersecurity practice.
How an engagement runs
- Discovery. Your systems, your release cycle, the risks that matter most and how you test today.
- Strategy. What to test manually, what to automate, the environments and test data, and how results are reported.
- Test. Test cases, execution and defect reports, with automation built alongside.
- Report and hand over. A clear release recommendation, the defects still open, and the test assets handed over to your team.
Planning a release, an upgrade or a go-live?
Tell us what you are building or changing, which systems it touches and when it has to go live. We reply with the questions that decide the testing scope, whether a project or a managed QA team.