Service · Software testing and QA

Test automation

Take a Kayseri furniture maker whose dealers order through a B2B portal. Every dealer has its own discount, payment-term surcharge and delivery terms, and the portal gets a plug-in or platform update nearly every week. After one unremarkable update, dealers were shown full list prices for three days running; the problem only came to light when an irritated dealer phoned the sales manager. An automated check would have caught it in minutes. A script signs in as a given dealer, puts products in the basket, compares the price against the expected discounted figure and, on any mismatch, warns the team before the release reaches production. We see test automation as a codebase that needs the same care as the product, not a gadget you install once and forget. That is why we do not try to automate everything. We begin with the flows that are checked most often and do the most damage when they fail.

Playwright
for web; Appium on mobile
API first
fast, stable checks
In the pipeline
on every change
Maintenance plan
included in every proposal

What the work covers in practice

The goal is not the biggest test count but a suite your team trusts and genuinely reacts to when it turns red.

Agree the scope with the engineer who will do the work

Scoring the candidates

Two questions decide each flow's score: how many times a month is it checked by hand, and what does a failure cost? Dealer login, special pricing, order confirmation and invoice creation usually come out on top.

The test pyramid

Most business logic is covered by quick unit and API tests, and only the most critical journeys go through the user interface. The suite finishes in minutes and does not collapse whenever the design changes.

UI tests

Playwright for browsers, Appium for mobile, with resilient selectors that survive a redesign and a layout your developers can follow at a glance.

Visual checks on output

Customer-facing documents such as invoices, dispatch notes and quotes are compared pixel by pixel with an approved reference. A shifted logo or an overflowing table stands out immediately.

Test data

Scripts create test dealers, products and prices and tidy them away afterwards. Nothing is copied from production, which is also the sound approach under KVKK.

Living in the pipeline

Tests run in parallel inside GitHub Actions, GitLab CI, Azure Pipelines or Jenkins. When one fails, its video, screenshot and log land in your team's Teams or Slack channel.

Taming flaky tests

Tests that pass one run and fail the next are quarantined on a separate list so they stop blocking the pipeline while we find the cause. A check the team has learned to ignore is worse than having none.

How we approach the job, from first call to handover

Start small, prove it, then grow. The first automated flows are usually running in the pipeline within a few weeks.

01

Discovery

Existing tests, CI set-up, release cadence and the scoring table for your flows.

02

First three flows

The top-scoring flows automated and shown to run steadily in the pipeline for a full week.

03

Growth

New flows in score order, with a short review alongside your team every fortnight.

04

Ownership

Either we keep maintaining the suite, or your developers take it over after training and pairing sessions.

Put automation beside your manual testers, not in their place. Machines confirm that known flows still work. Only a person notices that a new feature is confusing, that a label is misread or that an unforeseen path leads to an error. Hand routine checks to the pipeline and spend your team's time on exploratory testing.

Frequently asked questions

First we check which ones still earn their keep. Stable tests can stay; those that break constantly or that nobody looks at are either ported to Playwright or deleted. Porting everything blindly just carries old problems into a new tool.

We investigate straight away. If the cause is not obvious, the test is pulled from the main pipeline and tracked separately. Once people stop believing red results, the suite loses its value fast.

Yes, with Appium or, for Flutter apps, the framework's own testing tools. Mobile tests are slower and more fragile than web ones, so we keep the number low and focus on the most critical flows.

Whatever your team already uses, most often TypeScript. The tests live in your repository, the structure is documented and the hand-over includes a few pairing sessions.

Set-up is billed at €55 per hour plus VAT against an estimate agreed up front. Upkeep can run on hourly billing or within a Start, Business or Premium plan.

Let the pipeline take over your manual checks

What does your team click through by hand before each release, and how long does it take? We will put together a proposal for the first three flows.

Availability
Weekdays 09:00-18:00 Turkey time (GMT+3); an answer follows by the next working day
Calls
By video, over Microsoft Teams or Google Meet

The only cookies here are the essential ones: they keep the site running and remember the city you picked. Nothing is used for advertising or tracking. See our privacy notice for more.