Though developers may feel like they can look through the lens of a user, the only way to be certain of happy users is to let them test the product themselves. By performing these tests before moving to production, UAT will uncover defects and bugs before the end user is using it. And therefore, a properly executed UAT will save time, money, and frustration.

To actually perform UAT systematically, you need some way to register the tester’s findings. In our experience, companies often use Excel to support their UATs. Though that may look like an easy solution initially, it quickly turns into a mess when you want to manage multiple scenario’s and analyze results of multiple tests, performed by multiple testers. And let’s be honest, no one likes to dig through a big stack of Excel documents.

At Quatronic, we therefore started looking for an alternative. We wanted a tool that is simple, easy to use and easily maintainable. After some searching, it was clear that there are many tools available to perform UATs with. However, the majority was just too complex and extensive. Think of costly, large test management suites with functionalities that we were not going to use anyway. So we thought; why don’t we make it ourselves? After all, in our day-to-day work we use the low-code platform OutSystems which allows us to rapidly develop any app.