Logo

Mobile Messenger

Mobile Automation Testing, Mobile Testing, Software Testing Consultancy

Project Overview

What Mobile Messenger had in the testing processes when they came to us and what they got after they started working with us.

Before improvement

No automation tests
The regression testing took about 5 days
Poor and outdated test cases
Not informative bug reports

After improvement

Set up and use CI (continuous integration) based on Jenkins
Kept in touch with clients in-house testing team
QA Lead participated in the formation of test cases to automate testing at each sprint
Built an effective process with the customer development and testing teams
Time of regression testing decreased from 5 days to 46 hours
Mobile and desktop apps were covered with autotests for all main functionalities
Automation tests run on 3 real devices in parallel
All legacy test cases were updated
More than 3200 test cases created
Standardized bug reports with all required info and attachments
1700+
Automated tests
120+
Bugs found
3200+
Test cases designed
20+
Threads
40%
Critical and major bugs
QA Team:
4 Full-Stack QA Engineers
Project length:
1 year
Technologies & Tools
iOS
Android
Appium
Java
TestNg
Allure
Jenkins

The Challenge

Mobile Automation Testing of an instant messenger with end-to-end encryption algorithm.

With an instant messenger that uses end-to-end encryption algorithm, users have all conditions for secure messaging, secure calls, secure file sharing, etc. The client already had test cases, which were prepared by the in-house testing team.

The main task was to do automated testing of the full functionality of a mobile application on real devices, excluding the use of emulators.

In addition, it was necessary to reduce the time of regression testing which took about 5 days, before we started.

During the work, we also helped the client's in-house testing team with developing new test cases, since their test cases were poor.

The challenges we faced with:
  • Running tests using at least 3 devices in parallel;
  • Connecting a new device or replacing an existing one with minimal effort;
  • Problems of test logging;
  • Restarting failed tests;
  • WDA initialization instability;
  • And many others.
Read More on Our Blog

Achievements

We decided to use the Java + Appium + TestNG + Allure stack, and for the effectiveness of our solution, we used continuous integration based on Jenkins.

When working with the client, we constantly kept in touch with their in-house testing team. Our QA Lead participated in the formation of test cases to automate testing at each sprint. We have built an effective process with the customer development and testing teams.

Our solutions, in the form of starting work primarily on critical test cases, allowed the client to feel the results from the first week of cooperation.

As the result the time of regression testing decreased from 5 days to 46 hours.

Services Provided

Our engineers developed more than 1000 test cases in addition to the 2200 test cases from the client's in-house testing team

Mobile Automation Testing

4 Full-Stack QA Engineers were involved in work with the project. They successfully developed more than 1700 tests, which covers about 3200 test cases.

Mobile Testing

Our QA Lead was involved in the process of formation test cases for each sprint.

Software Testing Consultancy