Mobile application testing

The MobileUp team has its own QA Engineers. We get involved in the workflow at the stage of writing terms of reference. Then, we monitor the project quality until it is published in the app store. Certainly, our team continues to follow the project after its publication, but just in support mode.

Testing tasks

  • Feedback on product quality
  • Product quality assurance
  • Detection and prevention of bugs

MobileUp tasks

MobileUp offers two types of testing: auto testing and manual one. Most often, we prefer to use manual testing, but MobileUp has some huge projects and they need automated testing.

Auto testing

This method is applied when it is cheaper and faster than manual testing. This is not suitable for all projects, so we provide this service to our largest clients. For example, DMV Genie testing was automated (the group includes 14 applications). Automation was a necessary step to reduce testing costs in the future on this project.

The goal is to optimize the testing budget and free up the tester’s time to work on more complex cases.

Manual testing

The name hints that this type of testing involves a lot of manual work. Indeed, testers go through most of the scenarios manually. So we can get data on the state of the product very quickly and influence them promptly.

The goal of this testing is to obtain a complete picture of the product’s functionality and track dangerous points in time.

TestRail is used for testing. We usually keep our projects there: prepare test cases, do runs, and generate reports.

Functional testing

This is the testing that verifies compliance with the requirements of both the customer and the user. Find more info about types of testing that are selected depending on the goal and objectives below.

Analysis of documentation and layouts

The stage takes place before the beginning of the development. We study documentation and requirements, conduct a technical review of layouts.

Exploratory testing

Testing without case design based on functional background information is provided.

Our team can test even on POS devices. The photo shows testing devices for one of the projects — the Canadian POS system

Test case design

We make a list of test cases for the product. They should cover business logic, transition states, and bug handling.

Complete testing (full testing)

Deep testing of product functionality is provided. This may be required if the project has been refactored.

Test cases with high priority

Run of brief test on main project functionality when code has been already changed.

Analytics testing

We check each platform for display and correct collection of analytic data and events.

Database testing

The testing is used if a significant change has occurred in the database and it is necessary to check the deployment i.e how the release build lays on the one published in the app store.

Pixel Perfect

Pixel Perfect is a special coding technique in which screens match layout pixel by pixel (100%). We compare screenshots from real devices with a file in Figma and ring the alarm in case of any smallest gaps.

We know how to use test design techniques. Usually, our engineers prefer USE cases and boundary values. Sometimes diagrams and Mindmaps are also used.

Non-functional testing

We check how user-friendly, logical, fast, and reliable the product works.

  1. Exploratory testing

    This type of testing is suitable if there are no clearly defined cases.

  2. Performance testing

    Stress testing of the app is provided.

  3. Text consistency check

    We review all texts before release so as not to miss typos. There is the testing of localization, translation literacy, and correct text display.

  4. UI testing

    We make build reviews, compare layouts and actual screen states.

MobileUp has a large park with more than 60 models of old and new smartphones to search for bugs.

Static testing

We test the code and everything related to the application codebase.

  1. API and UX/UI

    Test the product for compliance with the API documentation and design.

  2. API testing

    Server health monitoring.

  3. Client/Server model

    Correct client-server interaction check.

Regression testing

The product is tested when changes are made.

  1. Related areas testing

    All functionality that could be affected by changes in the product is tested.

  2. Working areas testing

    The main functionality which should work a priori is tested.

Tools

  • Manual testing

    TestRail, Charles, Postman, Firebase Console, TablePlus, Android Studio, Xcode

  • Auto testing

    Behave, Toolium, Selenium, Appium
    PL — Python

  • Hyperion

    Hyperion is used for app testing. This is a debug tool to peek under the hood of the app and speed up manual testing.

Our QA engineers prefer Rubber duck debugging to manage complex tasks

Projects

  • We have achieved high rates of crash‑free for one confidential neobank

    We did functional, exploratory, regression testing, provided smoke tests, testing of localization, and UI. We also tested the compatibility of the app with the Telegram bot. The crash‑free rate of the app is 99,8. This means that less than 1% of users face crashes.

    Neobank
  • Automated testing for DMV Genie

    We have been working on the project since 2014. Today the group includes 14 apps that are carefully supported and constantly upgraded by our team. This year we realized that both MobileUp and the customer spend too much time and effort testing each application. The process has been automated to save the client’s time and resources.

    DMV Genie
  • Pixel Perfect is implemented for RBC

    Screens are made one-to-one with layouts because, not surprisingly, this is the industry standard. But there is a special Pixel Perfect layout technique that allows replicating of the layout through the layout page, down to the pixel.

    We made sure that the design and layout screens were identical on the RBC project.

    RBC Investment

Quality Assurance

Testing is an integral part of the development process. Testers don’t just help you find bugs in the app, but also prevent these bugs, find errors in logic, update databases, and monitor documentation. But the point is, they help to release a high-level product that matches the requirements of the customer and users.

Feedback

  • Logo Tutu.ru
    Evgeny LubaevProduct Owner Tutu.ru
    The team did an excellent job with both the first version of the app and its redesign. These guys have repeatedly proved their flexibility and excellent communication skills.
  • Logo Yami Yami
    Tima SergeevMarketing director, Yami Yami
    The previous app was not about food and had plenty of bugs. The new app is much better. Besides, we have improved the service efficiency. Now 10-13% of the total number of orders go through the mobile app.
Contact us