Testing & QA: the product works the way it was designed

We check web and mobile products before release and after every major update: from the first test plan to a regression suite that stays with your team. Based in Tashkent, working with clients in Russia, Hong Kong, Cyprus and Armenia.

Types of testing we do

The set depends on the product stage: a first release needs a full pass against requirements, a promotion needs regression of key flows, scaling needs load. We do not sell a package — we size the scope for a specific release.

• Functional — every scenario checked against requirements and user expectations, including negative paths and boundary values.
• Regression — a suite run before each release that catches what the new feature broke.
• Load — a load profile from real logs, target thresholds for p95 response time and error rate, runs until they break.
• Cross-browser and cross-platform — iOS, Android, desktop and mobile browsers on real devices and cloud device farms.
• Acceptance — the final check before hand-over against agreed acceptance criteria.
• Exploratory — unscripted sessions where requirements do not exist yet, with a findings log.

What the client receives

The result of testing is not "we checked everything" but documents a release can be accepted on and the next tester can work from.

• Test plan: scope, environments, devices, entry and exit criteria.
• Coverage matrix: which requirements are covered by which cases.
• A regression suite built for your product, in your tracker or in TestRail.
• Run report with results per environment.
• Defect register: steps to reproduce, environment, severity and priority, screenshot or screen recording.
• Load test protocols with charts and reproducible scenarios.

How the process works

1. A 20–30 minute call: product, stage, environments, release dates.
2. Test plan and estimate. If there are no requirements, we define the scope ourselves and agree it as an annex to the contract.
3. Runs in iterations with tracker access: you see coverage and defects as they appear, not at the end.
4. Report, act, hand-over of artifacts. By agreement we stay on for release support.

Tools follow your stack: Playwright and Postman for API and web flows, k6 for load, BrowserStack for devices, Charles for mobile app traffic, Jira or TestRail for tracking.

When testing matters most

• A release in a new country: different date, currency and address formats, different payment providers.
• A promotion or peak campaign: traffic several times above normal and no room for downtime.
• A change of development team: product knowledge left with the people.
• Integration with an external service: payment gateway, CRM, ad account.
• An audit before a deal or certification: an independent report on the product's state is required.