Software Testing and QA
Developers test that the code does what they meant. A tester checks what happens when a user does something nobody meant: pastes an emoji into the postcode field, presses Back halfway through payment, opens the same record in two tabs.
Our QA engineers work inside your team or alongside your supplier. They write test plans, test by hand where judgement is needed, and automate the checks that must be repeated before every release.
Testing reduces risk. It cannot prove that software has no defects, and we will not sign a statement saying so.
QA cost calculator
Our rates are published. Pick the role and move the sliders for an indicative budget.
Rate card
| Role | Hourly | Monthly* |
|---|---|---|
| Frontend / WordPress | $30 | $4,800 |
| Backend / API | $32 | $5,120 |
| Full-stack | $35 | $5,600 |
| Mobile (React Native / Flutter) | $35 | $5,600 |
| DevOps / Cloud | $40 | $6,400 |
| AI / Automation engineer | $45 | $7,200 |
| QA / Test engineer | $25 | $4,000 |
| UI / UX design | $28 | $4,480 |
*160 hrs/month full-time. Rates are indicative for planning, in USD (other currencies are converted at an indicative rate), and depend on seniority, contract length and timezone overlap. Longer engagements and multi-role teams are discounted — ask.
Kinds of testing and when each is worth it
Not every product needs every kind. We recommend the mix after seeing the application and its release history.
Exploratory testing
A tester uses the software with a goal and a time box, without a script. Good at finding the problems nobody thought to write a test case for.
Regression testing
The same checks repeated before each release to confirm that old features still work. The first candidate for automation.
API testing
Requests sent straight to the endpoints: wrong types, missing fields, expired tokens, another user's record ID. Faster and more stable than testing through the screen.
Browser and device coverage
Current Chrome, Safari, Firefox and Edge, plus real iOS and Android handsets at the screen sizes your analytics show.
Load testing
Simulated users at expected and peak volume, to find the query or endpoint that slows first.
Accessibility checks
Keyboard-only use, screen reader labels, colour contrast and focus order, tested against the WCAG criteria you specify. A formal audit is done by your auditor.
Basic security checks
Automated scans and manual checks for common weaknesses such as broken access control. This is not a penetration test, which needs a specialist firm.
Tools our testers use
If your team already has a framework in place, we write tests in it and do not start a second one.
- Browser automation
- PlaywrightCypressSelenium WebDriver
- Mobile
- AppiumXCUITestEspresso
- API
- PostmanREST Assuredpytest
- Load
- k6Apache JMeter
- Accessibility
- axeLighthouseNVDAVoiceOver
- Tracking
- JiraGitHub IssuesAzure DevOpsTestRail
Joining your team
You describe the product
What it does, how often you release and where bugs have hurt you before.
You meet the tester
We name a specific person. You speak to them and decide whether they fit.
A small first task
Usually a test pass over one feature. You see the quality of the bug reports before committing to more.
A test plan
A short document listing what is covered, what is not, and which checks will be automated first.
Steady state
Testing each release, growing the automated suite, and a weekly summary of what was found and what remains open.
What a bug report from us contains
A developer should be able to reproduce the problem without asking a single question.
- A title that names the symptom and the screen
- Numbered steps from a known starting point
- What was expected and what happened
- Browser, device and build number
- A screenshot or short recording
- Console and network errors where relevant
- Test data or account used
- Severity, with the reason for it
Will outside QA help you?
It helps when
- Developers are testing their own work and releases keep slipping back.
- The regression pass takes days by hand and is often skipped.
- You are about to launch and want a second pair of eyes.
- An agency built the software and you want an independent check.
It will not help when
- Nobody has time to fix the bugs that are found.
- Requirements are not written anywhere, so there is nothing to test against.
- You expect automation to replace all manual testing.
- You need a formal security or compliance audit. That is a different profession.
Practical points
Should we automate everything?
No. Automate stable, repeated checks: sign-in, checkout, permissions. Screens that change weekly cost more to keep automated than to test by hand.
Where do automated tests run?
In your pipeline, on every pull request or nightly. The test code lives in your repository and belongs to you.
Can a tester work with our overseas developers?
Yes. Our testers work India time and agree overlap hours with you. Written bug reports mean most of the work does not need a live call.
Do you test software built by someone else?
Often. We need access to a test environment, test accounts and whatever requirements exist.
What if the tester leaves?
We arrange a replacement and you approve the person. Test plans and scripts stay in your tools, so the knowledge does not walk out.
Tell us what you release and how often
Mention the platform, the release rhythm and the last bug that reached a customer. We respond within one business day.