Service · Software testing and QA

Test automation

Consider a Savinja Valley furniture maker that exports through a B2B portal used by dealers in Italy, Croatia and Hungary. Every dealer has an individual discount, payment period and delivery arrangement. Hardly a week passes without a plugin or library update. One unremarkable update left dealers looking at full catalogue prices for three days, and the firm learned of it only from an irritated customer writing to the head of sales. An automated check would have flagged it within minutes. The script signs in as a particular dealer, puts an item in the cart, compares the total with the discounted figure it expects and halts the release if the two disagree. For us automation is not a box to tick once. It is code, and like any code it needs care. So we do not chase full coverage; we start with whatever your people re-check manually most often and whatever causes the worst damage when it fails.

Playwright
browsers; Appium for phones
API layer first
quick, dependable checks
Inside CI
triggered by every commit
Upkeep plan
included in each proposal

Scope of the service

We want a suite your developers believe, so a red result gets attention instead of a shrug.

Check the scope with an engineer

Ranking what to automate

Two questions per flow: how many manual checks a month does it get, and what does a failure cost? Dealer sign-in, special prices, order confirmation and invoice creation tend to top the list.

Pyramid shape

Unit and API checks carry most of the logic; only the journeys that really matter run through the browser. The suite completes in minutes and does not collapse whenever the design is refreshed.

UI checks

Playwright in browsers, Appium on phones. Selectors are chosen to survive layout tweaks, and the code is kept simple enough for your developers to follow.

Comparing documents visually

Quotes, delivery notes and invoice PDFs sent to customers are diffed against an approved version. A logo that has moved or a table running off the page is spotted straight away.

Synthetic data

Scripts create dummy customers, items and price lists and remove them when finished. Nothing is copied from production, which also keeps you on the right side of GDPR.

Hooked into CI

Checks run in parallel on GitHub Actions, GitLab CI, Azure Pipelines or Jenkins. When one fails, its recording, screenshot and log appear in the team's Teams or Slack channel.

Unreliable checks

A check that flips between pass and fail is quarantined so it cannot hold up the main pipeline while we find out why. An untrusted check is worse than none.

How the work runs

We begin modestly, show results, then extend. Expect the first automated journeys in your pipeline within weeks.

01

Assessment

Current tests, CI configuration, how often you ship and a ranked list of flows.

02

Three flows to start

The top three automated, then a week of evidence that they run reliably.

03

Growing coverage

Further flows in ranking order, with a brief check-in alongside your team every two weeks.

04

Who looks after it

Either we maintain the suite or we train your developers and pair with them until they own it.

Automated checks free your testers; they are not a substitute for them. Scripts confirm that familiar paths still work. Only a person will notice that a new feature is baffling, that a label reads two ways or that users have found a route no one designed. Give the repetitive work to the pipeline and point human attention at exploration.

Your questions answered

We sort the useful from the useless. Reliable checks can stay put; ones that fail constantly or that no one reads are rebuilt in Playwright or dropped. Migrating the lot unexamined only relocates old headaches.

We investigate immediately. If the reason is not obvious, the check is quarantined outside the main pipeline and tracked on its own. When developers start ignoring red, the whole suite stops being worth much.

Yes, using Appium or Flutter's built-in tools. Mobile checks run slower and break more easily than browser ones, so we keep the number low and aim them at the journeys that matter most.

The language your team already works in, usually TypeScript. Everything sits in your repository with documentation, and we run a few pairing sessions at handover.

Initial build is billed at €50 per hour plus VAT, based on an estimate agreed beforehand. Ongoing upkeep can be hourly or covered by a Start, Business or Premium plan.

Let scripts do the repetitive checking

Which checks does your team repeat by hand before each release, and for how long? We will suggest where to begin with the first three flows.

When we work
Weekdays 9:00-17:00 CET, answers the same or next working day
Calls
Video meetings, Teams and Meet both welcome

We set essential cookies only: the ones that keep the site running and recall which town you chose. Nothing for ads and nothing that follows you around the web. Details are in our privacy and data protection notice.