logo

Testing and Product Acceptance

We check the product before your customers do. We answer to the client, not to the contractor — which is why we find what a development team has no interest in showing.

Ways to work
Functional testing
Integration testing
APIБД
Данные сходятся
Interface testing
Security testing
Уязвимость
Load testing
Пик нагрузки
User testing
СценарийИнтервью
A report listing every defectby severity, with the consequence of each one

When you need independent acceptance

An independent check earns its cost where a production bug costs more than the testing. One sign is enough:

You're accepting a contractor's work and don't know what to check

You have no QA engineers, or they're busy on other projects

The product was built in-house and needs an outside opinion

Bugs regularly reach users and cost real money

There's no confidence before a release that nothing will surface

You need specific checks: load, security, integrations

«Acceptance testing is an independent view: we answer to the client, not to the contractor.»
Kirill Kaplin — director, PROFSOFT

The checks we run

The mix of testing types is chosen for your product and its risks. Each card covers what we check and what you learn from it.

Functional testing and acceptance

We verify the product against the specification and stated requirements, scenario by scenario.

What you get

Documented proof of what was promised and what actually works — something to take to the contractor.

Integration testing

We check that data exchange with external systems and between modules is correct and stable. Tools: Postman, Charles.

What you get

Confidence that data isn't lost at the seams between systems — where things break most often.

Interface testing

We assess not just how the interface looks but whether it is logical and usable for the end user.

What you get

A list of the places where users stumble — before it shows up in reviews.

Security testing

We look for vulnerabilities and gaps in how confidential data is protected. Tools: OWASP ZAP, Burp Suite, Nessus.

What you get

Vulnerabilities are closed before anyone outside finds them.

Load testing

We simulate a peak influx of users to see whether the infrastructure holds. Tools: K6, JMeter, Yandex Tank.

What you get

A clear ceiling on load and knowledge of what fails first once it's passed.

User testing

We compare what real users expect against what the development team is delivering: scenarios and interviews.

What you get

Feedback from the people who will actually use it, not from the team that built it.

Ways to work together

We come in once for acceptance, reinforce your team, or rebuild the quality process end to end.

Product acceptance

A one-off independent check before you sign off a contractor's work.

Terms

  • Fixed scope and timeline
  • Report listing defects by severity
  • Verification against the specification
  • Retesting after fixes at a 50% discount

Dedicated QA team

When testing is needed continuously and you have no engineers of your own.

Terms

  • A team assigned to your product
  • Regular regression runs
  • Test plans and checklists stay with you
  • Working inside your process and tracker

QA process audit

When the team does test, but bugs still reach production.

Terms

  • Review of the current quality process
  • Assessment of coverage and test documentation
  • Automation recommendations
  • A plan to rebuild the process

How testing runs

Six stages from reviewing requirements to retesting. You see interim results, not only the final report.

1

Requirements review

Specification, scenarios and risk areas

2

Test plan

Types of testing, scope and tools

3

Preparation

Checklists, test data and environment

4

Testing

Running the checks and logging defects

5

Report

Defects by severity and their consequences

6

Retesting

Verifying fixes at a 50% discount

What the report contains

The report is written so you can take it to a contractor and make decisions with it, not file it away.

Testing scopeSource requirementsMethods and tools usedDetailed checklistCompliance with the specificationList of defectsSeverity of each defectBusiness consequencesSteps to reproduceFix recommendationsPriorities for reworkRetesting

See a sample report — it shows exactly what you receive.

Projects we have tested

Protector
Protector

Protector

Built an app to protect children in dangerous situations with live location sharing and fast help escalation

View case
PreventAge
PreventAge

PreventAge

Rebuilt an educational web platform with admin panel, payments and improved performance

View case
Farmakopeyka
Farmakopeyka

Farmakopeyka

A pharmacy-chain mobile app: search and order medicines, consultations, and a map of nearby stores

View case
CHTPZ Education Center
CHTPZ Education Center

CHTPZ Education Center

A mobile app for students, teachers, and parents in the Future of White Metallurgy program

View case
Feelo
Feelo

Feelo

Cross-platform app for tracking emotions and supporting mental wellbeing

View case
ORGHIM
ORGHIM

ORGHIM

Internal app for optimizing company business processes

View case
Samberi
Samberi

Samberi

Mobile app for a hypermarket chain

View case
Finn Flare
Finn Flare

Finn Flare

Mobile app for an online clothing store

View case
ROSTerm
ROSTerm

ROSTerm

A mobile plumbing catalogue: the installer puts a request together right on site

View case
Athletes Academy
Athletes Academy

Athletes Academy

A mobile app and admin panel: athletes earn a sports rank on video and get the award by post

View case
SportAktiV
SportAktiV

SportAktiV

A mobile app and admin panel for the Ryazan Region Ministry of Sport

View case

Testing FAQ

Because the contractor is checking their own work and is accountable for the deadline. We are accountable to you, so our interest is in finding problems rather than showing that everything is fine. That doesn't imply bad faith — internal testing and external acceptance simply have different goals.

A repeat check runs against checklists and test data that already exist: the preparation was done the first time and there's nothing to pay for twice. We verify that the reported defects are fixed and that the fixes didn't break anything nearby.

It depends on where a mistake costs you most. A product handling payments and personal data puts security and integrations first; a service with traffic peaks needs load testing. We agree the mix at the planning stage and explain the reasoning.

Yes, at any stage. The earlier the cheaper the fixes, but acceptance testing of an almost-finished product is still worth it: at least you'll know what you're signing off.

Cost depends on the amount of functionality, the mix of testing types and whether documentation exists: testing a product with no specification costs more, because the requirements have to be reconstructed. We estimate after reviewing the requirements, with a fixed scope and timeline.

The report is built to be handed straight to the contractor as a fix list: every defect with steps to reproduce, a severity and its consequence. Once the fixes land, we run the retest.

Discuss product acceptance

Tell us what the product is and what stage it's at. We'll propose a set of checks and the scope of work.