Beta Testing Report Summary

Our closed beta testing was ended on Nov 21st. We were happy with the response in the number of beta testers. We filled 92 out of 100 available slots. Many thanks to all the reported bugs and suggestions. In this post, we outline a few examples of our testers’ feedback.

During a period of three weeks, our internal testing team and outside beta testers identified 40 different issues. Half of those were front-end related, a third were UI issues, while less than a fifth had to do with the backend. If we look through the perspective of the nature of the issues: a third are considered bugs, a quarter are new feature requests, a sixth are missing functionalities, while roughly a quarter of reported issues are minor polishes.

Front-end

The majority of bugs were spotted by our internal team and logged into our improvements roadmap. The bugs were related to missing values, browser compatibility optimization, app misconfiguration, and, in a few cases, typos.

UX and improvement suggestions

Overall, the entire process is considered to be clear and the navigation OK, testers also said that the vocabulary used was clear. Some minor issues were spotted in the vouching and claim steps. Suggestions for improvements concern invitation steps and email communication. Our support team dealt mostly with issues caused by the MetaMask functionality.

Back-end

The minor backend issues with audit log management were resolved immediately.

All reported issues are already being dealt with by our development team, with a quarter already resolved. Suggestions for improvements and/or new features have been put into the backlog. We are happy to say that the product is functional, all transactions were logged on the blockchain, and that the entire process from registration to guarantee collection is working.