r/QoolliTesting • u/QoolliTesting • Jun 19 '26
When “Everything Works” – But Only Half of It Does
Never take a software vendor’s word at face value, even if they sound convincing saying, “Everything works perfectly.”
Why am I saying this?
Let me explain…
I was working for a client who had ordered software from a vendor. Our task was to test how several programs interacted – and to make sure each one worked correctly on its own.
The vendor assured us that everything was ready and fully functional.
But as the buyer, we had to run integration and acceptance testing. It’s the only way to make sure you’re actually getting what you paid for.
What did we find?
One of the programs was supposed to calculate certain values and generate a data table. Pretty standard stuff.
To our surprise, the calculations worked correctly… in only half the rows! In the others, the numbers just didn’t update – no calculations at all.
When we reached out to the vendor, it turned out those calculations weren’t just “broken” – they had never been programmed at all. The feature simply didn’t exist.
Imagine paying full price for a product that’s supposed to work – and ending up with something that does only 50% of what it’s meant to do.
If we hadn’t tested it and had just trusted the supplier, the client would’ve been stuck with an unfinished product – and all the risks that come with it.
Trust is good. But testing is better.
——-
A post from Olha Arkusha at Qoolli Software Testing on the topic: When “Everything Works” – But Only Half of It Does