Can you add tests to code you didn’t write?

Yes — that’s most of the work. We start with the riskiest flows and add end-to-end tests first, because they don’t require changing the code.

Do you do manual testing too?

Yes, before releases and for anything that is hard to automate, with reproducible bug reports your developers can act on.

Which stacks do you work with?

Mostly TypeScript/JavaScript web apps and APIs, but the approach works for any stack with a test runner and a CI.

Will our team be able to maintain the tests?

That’s the point. We write readable tests in your repository, run them in your CI, and document how to add new ones.

Software Testing and QA Services

What we test

Unit tests for business logic: prices, permissions, dates, currencies — the places where bugs cost money.
Integration tests against a real database and real HTTP handlers, not mocks of mocks.
End-to-end tests in a real browser for the flows users actually go through: sign-up, sign-in, payment, the core feature.
Regression suites in CI that run on every change, so an old bug stays fixed.
Manual testing before releases on real devices and browsers, with a clear bug list rather than a vague “something’s off”.

How we start on an existing codebase

1. Risk map

We read the code and talk to you about what breaks, what makes money and what scares you to change. That gives a short list of the flows that need tests first.

2. Safety net

We cover those flows with end-to-end and integration tests and wire them into CI. From that point, a broken release is caught before users see it.

3. Fill in

Unit tests go where the logic is dense. Every bug we fix gets a test that would have caught it.

4. Hand over

You get tests your team can read and extend, a CI pipeline that runs them, and a short guide on how to add new ones.

How we test our own products

Testing isn’t an add-on for us. The fewbase platform runs on roughly 370 test files across its services, from unit tests to browser-based end-to-end suites. Drones War has a deterministic game core with its unit tests running in CI on every push.

Tools we use most: Vitest and the Node.js test runner for unit and integration tests, Playwright for end-to-end browser tests, and GitHub Actions for CI. We adapt to your stack if it’s different.

Good fit if you…

are afraid to deploy because the last few releases broke something;
have a product with no tests and a team that has moved on;
want an outside QA pass before an important launch.

Software testing and QA