Rulebook of the business
Proposals, specs, minutes, or know-how only your staff carry around: we rewrite it as rules anyone can read. Where rules clash or were never recorded, we agree them with you first, then start raising defects.
Picture a hotel at Bled with 60 rooms. Its agency is delivering a new reservations module, linked to both the reception software and the channel manager, and every demo has gone smoothly. Now the awkward questions. Suppose a child has a twelfth birthday mid-stay: does the bed price change correctly? A reservation straddles the last low-season night and the first high-season one: whose cancellation policy wins? A guest books in German or Italian: is the confirmation fully in that language, or does Slovenian creep in halfway? Is the tourist tax itemised, and do a business guest's invoicing details survive the journey to the accounts? This is the territory of functional testing. Appearance is not the point; whether the software obeys your rules every single time is. We act as a neutral party, independent of the developer, and do everything remotely via a login to the test system. You finish with concrete, written grounds for either approving the work or demanding corrections.
Everything worth knowing before you put your name to the handover, captured in a form you can reuse for later releases.
Proposals, specs, minutes, or know-how only your staff carry around: we rewrite it as rules anyone can read. Where rules clash or were never recorded, we agree them with you first, then start raising defects.
Effort goes where behaviour changes: age thresholds, season boundaries, price tiers, minimum basket values, time limits that lapse at midnight, quantity discounts.
Č, š and ž in names and in search (does “Čeh” also find “Ceh”?), alphabetical order that handles those letters, four-digit postcodes, dates like 5. 10. 2026, comma decimals, and VAT at 22% or 9.5% on the right items.
All emails, PDFs and alerts reaching a user of the German, Italian or English version. We look for untranslated strings, wrong formats and pages that revert to Slovenian partway through.
A booking or order is tracked hop by hop: channel manager, Minimax or Pantheon, the payment provider in sandbox mode, and finally the shipping label.
After the developers repair things, we revisit the neighbourhood of each repair as well. Repairs that silently damage something nearby cause more handover surprises than anything else.
Each issue carries reproduction steps, input data, a screenshot and a priority, filed in GitLab, Jira, Azure DevOps or the developer's own tracker.
Modest apps take days. Bigger systems get tested piece by piece while development is still under way.
You show us the screens you care about, we discuss how the business works, and you give us a test login.
We ask which failure would hurt you most, order the test cases accordingly and estimate hours on that basis.
Planned cases, unscripted exploration, tickets, and a regression pass once fixes arrive.
Outstanding issues ranked by priority, then a brief video call: accept, accept with conditions, or send back.
Your test records should resemble your real customers. Typical test systems hold entries like “Janez Test, Testna ulica 1”. Real customers are named Žnidaršič, Šuštar or Čuk, live in hamlets with lengthy names and sometimes carry two hyphenated surnames. Deliberately including such people in the test set exposes many faults that would otherwise surface only once you are live.
Yes. We interview whoever knows the process and click around the system ourselves. Rules are documented along the way, and that document stays useful for every later upgrade.
Developers know the intended path and instinctively stay on it. An outside tester does the odd, unplanned things real customers do. Good agencies welcome the extra pair of eyes: catching a fault pre-launch is much cheaper than patching it afterwards.
No, and we would rather you did not. We use made-up or anonymised records that look realistic but describe no real person. Better for GDPR, and better test coverage too.
You get an hours estimate after the risk ranking; work is billed at €50 per hour plus VAT. Teams shipping frequently can fold testing into a Start, Business or Premium plan.
The issue list, the sign-off report and a set of reusable test cases for each future release. The most important ones can be automated at a later stage.
Tell us what the app does, who develops it and whether there is a sign-off date. We will come back with a risk ranking and an hours estimate.
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
No town by that name here. Check the letters, or settle for the nearest larger place. Our engineers work only over the internet, so Kočevje and Koper get precisely the same treatment.