Human Park

Introduction

Human Park is a web3 experience platform that allows users to self-express and show off their virtual identities, play battle royale, mini-games like tag, infection, shootout, and hide-n-seek together with other NFT characters, parkour in a 3D virtual world, teleport, attend in-game events, socialize, and explore many other playground areas.

Human Park NFTs are built on the Ethereum blockchain, whereas the gameplay is built on Unreal Engine.

Each Human Park player starts with creating their NFT avatar, which is nude by default. They can choose a gender and body composition, play with tattoo sizes and placement and apply other in-game cosmetics to achieve the desired look of their characters.

Human Park is available on Windows and macOS, and it’s a desktop install experience. The browser and mobile support are underway.

Challenge

When Virtually Human Studio and Spectre Studios turned to QAwerk, the Human Park platform was in an early development phase. The playground hasn’t been completed yet, but we had full access to the avatar configurator.

Our client wanted to open access to the early adopters of the game so that they could create their avatars, also known as Noods, customize them, and lock their designs. To reward the early adopters and increase the excitement around the game’s release, Human Park would airdrop the users’ avatar NFTs to their wallets with no gas fees.

Our task was to ensure that the users’ first interaction with the game is a positive and uninterrupted experience. We needed to carefully test the process of creating and customizing a Nood, a unique user avatar that reflects their identity.

On top of that, our client wanted to level up their QA process. Before partnering with us, they relied on bug reports and feedback from their Discord community and ran quick smoke tests in-house to identify major bugs.

With QAwerk’s help, they hoped to adopt a more thorough QA process that would result in healthier coding practices.

Solution

Since the game was in its infancy, we started with manual testing and outlined opportunities for automation in the future. Our client also wanted to ensure this new approach to QA put no strain on the in-house team and gave them enough time to acclimate to the new process. That’s why we started with the absolute essentials, such as:

• Installation Testing. At the time of our partnership, the game was available only for Mac users. We tested the installation client for macOS. We also checked if the connection with the MetaMask wallet was established without any hindrances. Our QA engineers went through every element on the screen before the login and then checked if the login itself was successful.
• Exploratory Testing. This type of testing is perfect for learning about the product and experiencing it as a first-time user. It allows receiving instant feedback with no documentation at hand. At the same time, the exploratory testing sequences can be later converted into functional test scripts. The ad-hoc, unstructured nature of exploratory testing also helps identify edge cases.
• Regression Testing. Regression testing is a must for rapidly developing games like Human Park. We performed several iterations of regression testing to ensure the updates had no impact on the intact parts of the code.
• UI/UX Testing. Human Park’s designers create all assets from the ground up and put much effort into making kick-ass graphics, be it in-game cosmetics, accessories, or additional collectibles. We ensured UI glitches didn’t undermine all this tremendous work and that users could fully enjoy the avatar creation process with no distractions or annoying malfunctions.

All of our work was documented in actionable bug reports. We also created Confluence documentation to describe our QA workflow step by step and keep everyone on the same page.