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.
A test suite your team understands, that runs reliably and whose maintenance is budgeted from day one.
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.
Pricing, discounts, availability and permissions are verified directly through interfaces, which is quicker and sturdier than any click through the UI.
A handful of well-chosen runs through the real interface, with robust selectors so design changes do not break tests every time.
Where appearance matters, such as invoice PDFs or product pages, we compare screenshots against an approved baseline and highlight any differences.
Scripts create test customers, items and prices and clean up afterwards. No copies of live data with real customer details.
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.
The first automated journeys usually run after two to three weeks. From there the suite grows at the pace your budget allows.
Which tests exist already, which journeys are critical and what the pipeline looks like.
Two or three key journeys automated and wired into the pipeline, proving it runs stably in your environment.
More journeys by priority, a weekly status and joint reviews with your team.
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.
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.
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.
Your enquiry has arrived
Our reply reaches you within one working day. Outages that leave your staff unable to work are dealt with first.
We could not find that town. Try another spelling, or choose whichever provincial capital lies closest; as everything is handled remotely, you get the same service in all nine Austrian states.