An application can sail through every demo and still trip up on its first Monday with real users. All it takes is a customer typing their Spanish tax number with a hyphen, an invoice that mixes lines at 21 % and 10 % VAT with an overall discount, or someone pressing the browser back button straight after paying with Bizum. Functional testing puts the software through those situations before your customers do. We check each feature against what was agreed with the development supplier or, where nothing was ever written down, against what the business expects. It makes no difference who built the software: your in-house team, an agency or us. The whole job is done remotely on a test or staging environment, and your live data stays untouched.
A list of bugs is only half the value. You also keep a growing set of test cases that anyone on your team can run again with every new version.
Before testing anything, we rank features by what a failure would cost. In a web shop, payment and delivery charges come first and the About page can wait. On an accountancy firm's client portal, sending documents to clients matters more than the search box.
If there is a functional spec, a set of user stories or a tender's technical specification, we read it looking for gaps and contradictions. An ambiguous rule caught before coding is settled in a phone call; found in production, it turns into weeks of patches.
Tax IDs for individuals, companies and foreign residents, IBANs from different banks, postcodes starting with zero, addresses with «s/n» or «3.º B», double surnames, accents and the letter ñ, and deliveries to the Canary Islands, Ceuta and Melilla, where local taxes replace standard VAT. Plenty of forms accept sample data and fall over with real customer details.
VAT at 21, 10 and 4 %, the equivalence surcharge for retailers, income tax withholding on invoices to freelancers, rounding per line versus rounding on the total and, where it applies, Verifactu or TicketBAI invoice records. A one-cent mismatch here usually ends in a call from your accountant.
We follow one transaction from start to finish: payment through a Redsys virtual POS, the entry in a3ERP, Sage 50 or Holded, a SEUR, MRW or Correos label and the email confirmation to the customer. A fault in the seam between two systems is invisible to both of their vendors.
We re-run the cases for whatever the developers touched and for areas that have broken before. It is the cheapest way to stop a basket fix from quietly breaking the customer account area.
Every defect goes into Jira, GitLab or Azure DevOps with steps, environment, data and expected result. At the end of the round you get a report on what was covered, what is still open and the risk of going live today.
The first round takes longer because the cases are written from scratch; from the second round onwards they are reused and the work gets much shorter. All we need is remote access to the test environment and a contact who knows the business.
A video call to see the application running and understand who uses it, what for and what would happen if each part failed.
Scope, browsers and devices, the data required and anything deliberately left out, with the estimated hours in writing.
We run the cases, log defects and re-check each fix as soon as the developer deploys it to the environment.
A go or wait recommendation, the defects still open, untested areas and the test suite ready for the next round.
A well-written bug report saves more hours than the test itself. «The invoice comes out wrong» triggers days of emails between you, the supplier and your accountant. «Order of 3 units with a 15 % discount, customer on the equivalence surcharge, PDF total is €0.02 off the on-screen total» gets fixed that same afternoon. That is how we write up every finding, with a screenshot or a short video.
Yes, and it is one of the most common requests. Many businesses commission an agency to build something and want an independent check before accepting delivery. We work on the test environment the supplier provides and log issues in whatever tool they use, sticking to reproducible facts rather than opinions.
No. We ask for a test environment with fictitious or anonymised data. If production is all there is, we agree with you which actions have no real-world effect, such as orders placed with a test payment method and cancelled afterwards.
That is normal for many small firms. We begin with exploratory testing, using the application the way a new employee would, and record how it really behaves. The result is a first functional description that will also help any future supplier.
It is charged by the hour at €75 per hour + VAT, with a cap set in the test plan that is never exceeded without your approval. If you release monthly or weekly, recurring testing can be folded into a Start, Business or Premium plan with a fixed monthly fee.
Tell us what the software is, who develops it and what worries you. We will send a test plan with an estimate of hours.
Your request is with us
Expect an answer within one working day. A reported fault that has halted your team is handled first.
No match found. Try another spelling, or go with the closest provincial capital: every job is done remotely, so the location makes no difference to what we deliver anywhere in Spain.
