Quality Assurance Setup and Testing for Mobile Gaming & NFT Platform

Testing for Mobile Gaming

Industry

Mobile games, NFT

Country

France

Type of Service

Manual testing

Cooperation Type

Full-time

Project Type

Mobile testing

Overview

Sport Faction is a Web3 mobile game studio that combines Mobile Gaming, Sports, and NFTs. They aim to create a gaming environment where players smoothly transition between different exciting worlds. Sport Faction’s own game, “Football Faction,” allows users to create and manage teams based on real player performances during sports championships.

Challenge

The client needed to set up the QA process from scratch:

  • Define test scope and coverage for the platform.
  • Prepare test documentation.
  • Run testing and integrate it into the existing development workflow.

Having a QA engineer with experience in mobile game testing was a preference.

Solution

The QA engineer works with the application’s frontend and partial backend. Preparing test documentation for it entailed the following steps:

  1. Description of the release flow for better understanding by all parties.
  2. Development of the task flows (user stories).
  3. Description and approval of the bug life cycle (defect reporting and management).

The work with the product directly started with exploratory testing. It is an effective way to get familiar with the product and prepare test cases for further work. Then, the QA engineer defined the types of testing that would be necessary for the product.

  • Functional and UI tests – the core checks for feature acceptance.
  • Performance tests – run after code optimization and environmental changes.
  • Compatibility tests – verifying the software’s behavior on various devices.
  • Smoke tests – executed before every release on core functionality.
  • Regression tests – meant to confirm that functionality works as expected after code iterations.

The team works in three-week sprints with dedicated Kanban boards. A straightforward task flow makes it easy to understand and track the QA input. The QA engineer participates in sprint planning, reviews, retrospectives, and monthly team meetings.

Results

  • 18% of detected bugs were critical. They affected the core functionality, making the software complicated or impossible to use.
  • The team fixed over ¾ of the bugs during the first four months, within sprints prior to releases.
  • Detected errors in design, requirements, and functionality that were taken into consideration.

Let’s Start a New Project Together

QA Madness helps tech companies strengthen their in-house teams by staffing dedicated manual and automated testing experts.

Anastasiia Letychivska

Head of Growth

Ready to speed up the testing process?