Send a few lines about your business and what you need. Your request goes straight to Vlad, our founder, who replies with the next steps.
QA and testing
QA and testing built into every project
Every website and app we build is tested by our QA specialists before your users see it: manual testing, automated tests on every release, and accessibility and speed checks. It is part of our projects and support plans, not an extra.
- Every release
- tested before it goes live
- Manual + automated
- people and test scripts
- WCAG + speed
- checked on key pages
What does QA catch?
The problems that cost the most when your users find them first.
Broken forms and checkouts
A form that fails silently loses leads and orders.
Bugs on some phones
Layouts and features that break on certain devices and browsers.
Things that used to work
A new feature quietly breaks an old one.
Barriers for some users
Pages that keyboard and screen reader users cannot use.
Slow pages
Pages that load too slowly on phones.
Data errors
Wrong totals, lost records and edge cases nobody tried.
What is included?
Testing from the first build to every later release.
- 01
Test plans
What to test for each feature, agreed before development.
- 02
Manual testing
People testing on phones, tablets and desktop browsers.
- 03
Regression testing
Earlier features checked again before every release.
- 04
Automated tests
Scripts that check key flows, such as sign-up and checkout, on every change.
- 05
Accessibility checks
Key pages checked against WCAG 2.2 AA.
- 06
Speed checks
Page speed measured with Google PageSpeed before launch.
- 07
Bug reports
Clear reports with steps, screenshots and priority, fixed before release.
Example
Magiczna Kraina: tested before launch
Before this nursery and kindergarten's new website went live, we tested it on phones and browsers, in both languages, and against accessibility and speed targets.
- 0
- accessibility violations on 12 key pages
- 100
- PageSpeed score on mobile and desktop
- 2
- languages tested
How does testing fit into a project?
From the first demo to every update after launch.
- 1
Plan
Test cases written from the agreed features.
You: review the key flows
- 2
Test each build
Manual tests on every demo build.
You: join the weekly demo
- 3
Automate
Key flows covered by automated tests.
- 4
Before release
Regression, accessibility and speed checks.
You: approve the release
- 5
After launch
Tests run again on every update.
How is QA priced?
QA is included in the price of every project and support plan. There is no separate testing bill, and no release goes out untested.
QA questions
Yes. Testing is part of every project and support plan we quote.
Our QA work is part of the software we build and support. If another team built your app, we can start with a code review as part of a modernization project.
Current iPhones and Android phones, tablets and the main desktop browsers: Chrome, Safari, Edge and Firefox.
Yes. Key flows, such as sign-up, checkout or sending a form, get automated tests that run on every change.
We check key pages against WCAG 2.2 AA with automated tools and by hand, including keyboard use and screen reader labels.
