Service · Software testing and QA

Test automation

Picture a plumbing supplies wholesaler running its B2B shop on Shopware. Every customer has individual prices, volume discounts and delivery terms, and plugin or platform updates land almost every week. Once, a harmless-looking update meant installers saw list prices instead of their negotiated rates for three days. It only came to light through an angry email. Automated tests would have caught it in minutes: a script logs in as a specific customer, adds items to the basket and checks the price, on every update, before anything goes live. Automation pays where checks are repeated often and mistakes are costly. That is why we begin with a list of the journeys where an unnoticed fault would cost the most money or trust.

Playwright
for web, Appium for mobile
API first
fast and stable
Visual
screenshot comparison where useful
Upkeep plan
part of every quote

Everything this covers

A test suite your team understands, that runs reliably and whose maintenance is budgeted from day one.

Settle the details with an engineer

Choosing candidates

We list journeys by how often they are checked and how much damage a fault would cause. Sign-in, customer-specific pricing, checkout and invoice dispatch typically top the list.

API tests for logic

Pricing, discounts, availability and permissions are verified directly through interfaces, which is quicker and sturdier than any click through the UI.

End-to-end with Playwright

A handful of well-chosen runs through the real interface, with robust selectors so design changes do not break tests every time.

Visual comparison

Where appearance matters, such as invoice PDFs or product pages, we compare screenshots against an approved baseline and highlight any differences.

Test data on demand

Scripts create test customers, items and prices and clean up afterwards. No copies of live data with real customer details.

Pipeline and alerts

Hooked into GitHub Actions, GitLab CI, Azure Pipelines or Jenkins. When a test fails, a message with video and log arrives in Teams or Slack.

Our working method

The first automated journeys usually run after two to three weeks. From there the suite grows at the pace your budget allows.

01

Analysis

Which tests exist already, which journeys are critical and what the pipeline looks like.

02

Pilot

Two or three key journeys automated and wired into the pipeline, proving it runs stably in your environment.

03

Expansion

More journeys by priority, a weekly status and joint reviews with your team.

04

Upkeep

We adapt tests to new features under a monthly plan, or hand over to your developers with training.

Test code is code and needs looking after. Every new feature and design change means tests must be adjusted too. Set aside a fixed share for this, typically a fifth to a third of the original effort per year. A neglected suite turns red within months, gets ignored and is finally switched off.

Frequently asked questions

Yes, that is often the aim. We write tests in your team's language, usually TypeScript or the back-end language, document the structure and provide training over video.

Flaky tests like that are fixed at once or temporarily taken out of the pipeline. A test nobody trusts does more harm than a missing one.

With infrequent releases and stable software, often not. If you ship at least monthly, a small suite covering the most critical journeys usually pays for itself within the first year.

You do. They sit in your repository and the rights are covered by the contract.

Set-up by time at €110 per hour plus VAT following an upfront estimate; upkeep either hourly or as part of a Start, Business or Premium plan.

Let us automate your most important checks

Which journeys do you currently check by hand, and how often do you release? We will suggest a pilot covering two or three of them.

Availability
Monday to Friday, 8:00-17:00 Austrian time (CET/CEST), reply within one working day
Meetings
By video on Microsoft Teams or Google Meet

We only use cookies that are technically required: to run the website and to remember the location you picked. There are no advertising or tracking cookies. Details are in the privacy notice.