QA strategy, test plans and release criteria
What to test, how and when, with clear criteria for when a release is ready to ship.
QA and Testing
QA and software testing for confident releases
Independent quality assurance woven into delivery, from exploratory and regression testing to automated suites in CI, so releases go out on schedule without surprises.
Bugs found by customers are the most expensive kind. They cost support time, reviews and trust, and they are harder to trace than bugs caught before release. Quality assurance moves that discovery earlier, where fixes are quick and cheap.
Our QA engineers work inside the delivery process rather than at the end of it. They write test plans from the requirements, test each feature as it is built, and keep a regression suite so old features keep working as new ones arrive. Repetitive checks are automated and run on every change in your CI pipeline.
We test on real devices and browsers, check APIs and performance under load, and report issues with clear steps to reproduce, so developers can fix them without guesswork. We can test products we built or products built by your own team.
What is included
Manual, exploratory and regression testing
Structured test cases for each feature, exploratory sessions that find unexpected issues, and regression runs before every release.
Cross-browser and real-device testing
Testing across Chrome, Safari, Firefox and Edge, and on real iOS and Android devices with different screen sizes and OS versions.
Automated unit, API and end-to-end suites
Tests written with Jest, Cypress, Playwright, Detox and similar tools, running automatically on every pull request.
Performance and load testing
Tests that show how your system behaves under expected and peak traffic, and where it slows down first.
API contract testing and documentation
Checks that your APIs return what they promise, with Postman collections and Swagger docs kept up to date.
How we work
- 01
Review and plan
We review the product and requirements and write a test plan with priorities and release criteria.
- 02
Test cases and setup
Test cases, environments, test data and device coverage prepared before testing starts.
- 03
Test and automate
Features tested as they are built, with repetitive checks automated in your CI pipeline.
- 04
Report and sign off
Clear bug reports with steps to reproduce, retesting of fixes, and a release report before each launch.
Tech stack
- Manual testing
- Cypress
- Selenium
- Jest
- Puppeteer
- Postman
- Mocha
- Detox
- Swagger
Pricing
Every project starts with a free discovery call and a written estimate split into milestones. Choose the model that fits:
- Fixed-price project. A written scope split into milestones, each with a fixed price and deliverable. Best when requirements are clear.
- Hourly. Pay for the hours worked, with time tracked and reported. Best for ongoing changes, audits and evolving scope.
- Dedicated developer or team. Developers assigned to you on a monthly contract, working your business hours as an extension of your team.
- Maintenance and support. 24/7 monitoring against a 99.9% uptime target, plus fixes, updates and small features after launch, as needed or on a monthly plan.
FAQ
QA and Testing questions
What clients usually ask before starting a qa and testing project with us.
Another question? Email info@mercurysols.org.
Can you test a product built by another team?
Yes. We start by learning the product and its requirements, then test it like a new user and a demanding one, and report issues in your own tracker.
Manual or automated testing?
Both. Automation suits repeated checks such as regression and API tests. Manual and exploratory testing is better for new features, usability and edge cases. Most products need a mix.
Which devices and browsers do you test on?
Current versions of Chrome, Safari, Firefox and Edge, plus real iOS and Android devices. We agree the device list with you based on your users' analytics.
Do your own development projects include testing?
Yes. Testing is part of every build we deliver, with acceptance criteria for each milestone and automated tests on key flows.
How do you report bugs?
In your tracker, such as Jira, Linear or GitHub, with steps to reproduce, expected and actual results, screenshots or recordings, and a severity level.
Other services
Have a project in mind? Let's talk.
Tell us what you want to build. New builds, ongoing work or maintenance, on fixed-price, hourly or dedicated-team terms. We reply within 1 business day.
- We read your brief and reply within 1 business day
- A short call to agree goals and scope
- A written proposal with milestones and cost