Service · Software testing and QA

Functional testing

Imagine a hotel in Tyrol getting a new booking engine for its own website, linked to a channel manager and the property management system. In the agency's demo everything looks fine. But how does it work out the local tourist tax for a child who turns fifteen mid-stay? What happens to a booking that straddles the change of season, when off-peak cancellation terms differ? And does the confirmation email arrive in Italian if the guest browsed the site in Italian? Functional testing answers questions like these. It does not ask whether the software “basically works”; it asks whether every rule that matters to your business behaves correctly, awkward corner cases included. We work entirely remotely on a test environment, whoever did the development, and give you a sound basis for formal acceptance.

Send an enquiry Inclusions overview

Boundary values

where rules flip over

Acceptance test

before the final payment

Severity levels

critical down to cosmetic

Test cases

reusable for every release

Everything this covers

From pinning down what we are testing against to a report on which you can accept or reject a delivery.

Settle the details with an engineer

Agreeing the test basis

Quote, specification, tickets or simply what your staff know: we record what the software is measured against. Where rules are missing or contradict each other, we settle that with you before logging defects.

Boundaries and equivalence classes

Rather than hundreds of random inputs, we target the points where rules change: age limits, season changes, quantity tiers, minimum order values, deadlines at midnight.

Austrian specifics

VAT at 20, 13 and 10 %, reverse charge for business customers with a VAT ID, addresses with staircase and door numbers, four-digit postcodes, umlauts and ß in names, dates and decimal commas in the right format.

Multiple languages

Screens, emails and PDFs in every language offered, truncated translations, wrong currency or date formats and language switches that get lost mid-journey.

Interfaces

Does the booking reach the channel manager, does the order land in BMD or RZL, does dispatch produce a valid Österreichische Post label? We trace transactions across system boundaries.

Browsers and devices

An agreed matrix of browsers, phones and tablets taken from your analytics, not from a list of every conceivable combination.

Graded defect reports

Each finding with steps, data, a screenshot and a rating from critical to cosmetic, logged in Jira, GitLab, Azure DevOps or your supplier's tracker.

Our working method

For a modest application a cycle of a few days is often enough. Larger systems are tested in stages alongside development.

Introduction

A video session with a demo of the application, clarification of business rules and access to the test environment.

Test design

Test cases ordered by risk, an agreed scope and a written estimate of hours.

Execution

Testing, defect reports and retests of fixes, with brief progress updates for you and the supplier.

Acceptance report

Open defects by severity, the scope covered and a plain recommendation on acceptance.

Tie the final payment to an acceptance test. Many agency contracts include acceptance, yet in practice it shrinks to a quick glance at the home page. Agree upfront that no critical and only a set number of major defects may remain open. Both sides then know where they stand, and you avoid later arguments about what “finished” means.

Frequently asked questions

We start with exploratory testing and conversations with the people who know the workflows. That produces documented business rules and test cases, and as a by-product you gain a description that helps with every future change.

Good agencies welcome it, because defects are cheaper before go-live and a clear report keeps discussions factual. We log findings neutrally and reproducibly, without judgement.

Only by exception and by arrangement, for example with test payments cancelled immediately. The norm is a test environment with invented or anonymised data.

We charge €110 per hour plus VAT, based on the estimate of hours in the test design. With regular releases, testing can also be included in a Start, Business or Premium plan.

As many as your users really use. Four to six combinations usually cover the bulk; rarer ones are spot-checked.

Related work in the same area

Open the full area page

Service Load and stress testing Measuring how much your system can take instead of discovering it on the day Service Test automation Automated tests that show within minutes of any change whether everything still works Service Usability and UX testing Discovering why people give up on your website or app Service Penetration testing Authorised attacks on your application to find holes before real attackers do

Have your software checked by us

What is the application, who builds it and is an acceptance coming up? We will send you a test design with an effort estimate.

Email
office@apply.at

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

By ticking this box I allow Apply to process my details for the purpose of answering this request (see our privacy notice for details)