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

Test automation

Automation pays off where the same scenarios are checked over and over. With a yearly release it is unnecessary. With a fortnightly release the manual regression run becomes the main brake on the whole process.

Send a request What is included
The run
minutes instead of days
The build
checked automatically
Отбор
the key parts, not everything
Отчёт
what failed and at which step

What the work includes

We automate not everything but what repeats often and has settled down. Chasing full coverage costs more than the benefit it brings.

Discuss the scope

Selecting the scenarios

First of all what is critical to the business and gets tested most often.

Writing

The tests are made resilient to cosmetic interface changes, otherwise maintenance eats the entire benefit.

Test data

They are prepared and cleaned up so the runs do not affect one another.

Running on each build

The tests run automatically on every build rather than when somebody remembers them.

Reporting

A clear result showing the step at which it failed, with a screenshot.

Maintenance

Updating the tests as the product changes. That is continuous work rather than a one-off project.

How it goes

The first tests appear in two or three weeks; the noticeable effect comes once the main paths are covered.

01

Расчёт

We count how much time the manual regression run takes today. From that you can see whether automation will pay off.

02

The basis

The execution infrastructure, test data preparation, the reporting system.

03

Coverage

We write the tests in turn, starting with whatever breaking would be most visible.

04

Upkeep

We update them as things change and deal with flaky tests.

A flaky test is worse than no test. When a test fails again and again for no real reason the team stops reading the results, and genuine breakages get ignored along with the noise. Such tests are either fixed at once or deleted without regret.

Questions and answers

No. Automated tests run what has already been described quickly and tirelessly. Only a person can find an unknown problem in a new scenario. Automation removes the routine, not the people.

With infrequent releases, a rapidly changing interface and prototypes. If the product is redrawn every month the tests will have to be rewritten faster than they can pay off.

Sensible coverage rather than maximum. Usually the paths that bring in money and the places where defects have already occurred are enough. Chasing a coverage percentage produces tests for the sake of tests.

More in this area

Open the area
Service Functional testing Testing the working scenarios before release Service Load testing Поведение системы под пиковым трафиком Service UI/UX testing Testing interface usability with real users Service Security testing Finding vulnerabilities before others do

We will move the tests to automation

Tell us how often you release and how long the manual run takes. We will work out whether automation pays.