QA and testing
Every change,
tested before it ships.
Automated tests on every pull request, so you can release with confidence.
What’s included.
- 01
Test strategy
What to test and at which level, based on risk.
- 02
Unit and integration tests
Fast, and next to the code.
- 03
End-to-end with Playwright
The key journeys, in real browsers.
- 04
Visual regression and reports
We catch unwanted design changes.
How we do it.
A safety net of tests that runs by itself on every change.
Test pyramid
Many fast unit tests, some integration tests and a few end-to-end ones: just enough.
End-to-end with Playwright
We automate the key journeys, like signing up or paying, just as a person would.
In CI, on every PR
Tests run in GitHub Actions on every pull request; if something fails, it doesn’t merge.
Visual regression and reports
We compare screenshots to catch visual changes and share a clear report.
What we use.
Proven tools, chosen for your project.
Playwright- Vitest
- Testing Library
- GitHub Actions
- Storybook
- Lighthouse
- k6
Questions.
Does this replace manual testing?
Not entirely. We automate the repetitive part so manual testing can focus on what’s new.
Can you add tests to an existing project?
Yes. We start with the most critical journeys and grow from there.
Which browsers?
Chromium, Firefox and WebKit (Safari’s engine), on mobile sizes too.