For business For individuals For public sector For partners
Call an engineer Help
Payment by invoice Card payment Check a payment Closing documents
Русский Қазақша English
Sign in
Services
Solutions
Pricing
Cases
Training
Company
Contacts
Русский Қазақша English
All services
Basic Up to 15 seats, weekday support from 9 to 18 Standard Up to 50 seats, round the clock, servers included Premium Named engineers, response within fifteen minutes Project One task, price agreed in advance Free IT audit Five days of review and a written report
IT outsourcing and support Tickets, on-site visits and a duty line all week Support levels and SLA Response time written into the contract System administration Windows and Linux, domain, virtual machines IT infrastructure Starter setup, survey, virtual desktops Networks and telecom Cabling, diagrams, testing and supervision Low-voltage systems Cameras and access control Cloud services and hostingNew Virtual servers, 1C platforms, file storage Backup Copies, off-site storage, recovery procedure
Regulatory requirements Personal data, paperwork and technical measures System and data protection Network, software, databases and a filter in front of the site Monitoring and control Duty monitoring, vulnerability scanning, antivirus Security tools Selecting and rolling out security tools, private channels
Websites and web development From a couple of pages to a wholesale platform E-commerce and integrations Accounting sync, payments, delivery, marketplaces Bitrix24 and portals Portal, deal pipeline and licences Custom development Software built for the task and mobile apps Testing and QA Scenarios, load testing and automated checks
Artificial intelligenceNew Use cases, rollout plan and staff training Data and analytics Clean reference data, dashboards, scan recognition Consulting and audit Strategy, system and architecture assessment Marketing Channel review, deal stages, consulting
Workplaces Desktops, laptops, peripherals and consumables Servers and networks Servers, storage, switches and power supply Retail equipment Cash registers, marking codes, scanners and scales Software Antivirus, developer and admin tooling Training For a company, for a group and one to one
Not sure where to start? We review your infrastructure free of charge in five days Request an audit
All solutions
Data localisation Moving systems and data to a site inside the country Personal data protection Paperwork and safeguards before an inspection arrives Office relocation Network, servers and staff workplaces at the new address Opening a branch One equipment standard and a link to head office Remote work Virtual desktops, access to accounting, private channels Downtime protection Backups, monitoring and an incident procedure
Retail and e-commerce Registers, codes, store and one stock across channels Manufacturing Shop-floor network, servers and production accounting Healthcare Patient data and uninterrupted operation Construction Links to sites, workplaces and design software Logistics Warehouse, data collection terminals and data exchange Public sector Registered software, portals and protection requirements
Small business Up to 15 seats, simple support without servers Medium business Servers, network and round-the-clock duty Large business A dedicated team, firm deadlines, reporting Branch network The same IT at every location
Didn't find your scenario? Describe the task and we will put a solution together Send a request
About us Who we are and how the work is organised Special offers What we offer right now and on what terms For partners Terms of cooperation and commission Payment Invoice, card and closing documents Contacts How to call, write and get to us
Услуга · Тестирование и QA

Functional testing

The aim is to confirm the product behaves correctly not only on the happy path but on all the others too. A defect found before release costs several times less than one reported by a customer.

Send a request What is included
Scenarios
documented and reusable
Before release
a full run
Defects
with steps to reproduce
Риски
listed in writing

What the work includes

The main value lies not in individual defects found but in the accumulated set of scenarios run from version to version.

Discuss the scope

Requirements analysis

We read the specification and find contradictions before any code is written. Defects caught here are the cheapest of all.

The scenario set

Documented tests with expected results, suitable for reuse.

Functional checks

The main paths, boundary values, the reaction to deliberately invalid data.

Re-testing after fixes

We confirm the new work has not broken what already worked. This is where most regressions are found.

Writing up the defects

The steps, the environment and the expected behaviour so the developer does not have to guess.

The verdict

What was tested, what fell outside the scope and which risks you accept by releasing.

How it goes

The first cycle takes longer because the scenario set is written from scratch. Subsequent runs go considerably faster.

01

Getting to know it

We get to know the product and establish what is critical for the business and what is secondary.

02

План

We define the scope and boundaries of the testing. It is impossible to check an infinite set of variants.

03

The run

We walk the scenarios, record what we find and re-check after the fixes.

04

The verdict

A release readiness statement listing the uncovered areas and the remaining risks.

A defect without steps to reproduce will be closed by the developer as unreproducible. A message saying «checkout does not work» comes straight back and travels between people for weeks. Precise steps, data and environment cut the fix time several times over.

Questions and answers

They do test, but they walk the path they had in mind and do not notice their own assumptions. A separate person tests exactly what the author did not think of: invalid input, a lost connection, a button pressed twice.

Roughly a quarter to a third of the development time. Less than that and only the main paths are covered, so some defects will reach users. Sometimes that is a deliberate and perfectly reasonable choice.

Yes, and it is a common request: the system is live but the quality raises questions. We start by studying it and build a set of scenarios from the actual behaviour, since documentation as a rule does not exist.

More in this area

Open the area
Service Load testing Поведение системы под пиковым трафиком Service Test automation Automated tests for regular checks Service UI/UX testing Testing interface usability with real users Service Security testing Finding vulnerabilities before others do

We will test your product

Describe the system and what worries you. We will draw up a test plan and estimate the effort.