Test, Test, and When You Think Everything is Good, Test Again

September 16 2017, 12:57pm

When developing, it's so easy to become blind to issues that might be present. When you know the in's and out's of a product or service, navigating it becomes a breeze. It is oddly in this ease that many problems can remain hidden. Testing an application or website with an outside group of users is a great way to uncover hidden obstacles.

Pokemon Go having some issues

Someone forgot to change the dummy text.

Even when testing though, it becomes easy to ignore one-off problems as fringe cases that may only occur once in a blue moon. Depending on sample sizes, this may very well be the case—especially if that sample size is huge. More likely, a problem a test-user may have though is evidence of a larger problem with the application. Take these problems to heart and use this phase of testing as a way of making the product or service better.

Just when you feel like things are ready, test again. Oftentimes, fixing one problem results in another issue coming up.

Lugia, where are you?

Where's Lugia and the correct gym leader?

When you're ready for release, let the application out in the wild with the assumption that more problems will be uncovered. Be grateful to users when problems are uncovered and treat users well when impediments to using the application are found.

Brave Frontier

Photo by Brave Frontier Wiki

Most games have some kind of bug. A game I played that treated users well for problems, mostly related to connectivity issues was Brave Frontier. They offered in-app currency and bonuses that helped keep users, not only from leaving the app, but actively engaged.

Focus on the experience, test, and treat users like gold to keep them coming back time after time.

Have you experienced any bugs before? What happened as a result of reporting them?