Software Testing for Fitness App Case Study

What is a Fitness System?

The innovative product of our colleagues from San Francisco was not just a fitness application, but a whole system, which is still unique in the fitness world.

The system includes:

The tablet, which contains videos and specialized software that helps create your individual training schedule and track the intensity;

The full-size equipment for training, which is aimed at different muscle groups.

How Did We Become a Part of the Team?

We got involved in the development process when the application was already in the beta-phase, just under a year was left before the market release; however, over half of the code was written already. To ensure that the developed interface is adapted for the native device, the customer sent us two tablets, which at first sight looked like a TV, as it needed to be connected to a wall outlet.

Through the course of our work, we used the , Realm database, SQLite, Mockito
and Robolectric Frameworks.

Problem

The application was being developed for a specific device. And the first problem we encountered was its uniqueness. The tablet called Hercules was not available for sale. It was a kind of a custom device, and we couldn’t use similar devices.

Solution

As the testing was performed by the customer, it was necessary to avoid the major bugs and to provide a high-quality code. The fitness system included the power equipment, but as we had only the tablet. So only the visual software part was available for testing.

To cut the testing time, we made a decision to engage our QA engineer for smoke testing of the features.

Result: You got a happy and satisfied customer.

Across Different Time Zones

We were working together with designers, development team and software testers to bring up the best product possible. So maintaining a good and fruitful communication was a key factor here – they were all thousands of kilometres away. As the project was a start-up, communicative and working processes weren’t as smooth as it seemed to be from the first sight. In addition, the customer had no experience of working with the team members in different time zones. So integration into the process was some kind of a challenge.

To cut the testing time, we made a decision to engage our QA engineer for smoke testing of the features.

How Did We Start?

Result:

The Major Application Improvements

The innovative product of our colleagues from San Francisco was not just a fitness application, but a whole system, which is still unique in the fitness world.

Key Project Results