Magora - Cooperation for better quality

about company

Magora is a Web & Mobile Development Company that offers digital services to businesses across a broad range of industries, including Pharma & Medtech, Edtech, eLearning and eCommerce. Whether a B2C or a B2B project, iOS or Android app, first of all, Magora takes the time to understand customer’s goals, product and the end-user’s needs. Their Software development cases are loved by users for their convenience and appreciated by customers for the real value they add to your business.

Luxe Quality provides QA engineers for the Magora. Together, we successfully assemble productive teams and care about the release of a quality product.

This case will describe the testing of the English application for the provision of short-term (hours-days) and long-term (years) car insurance services.

the process of choosing a candidates

For the project, it was necessary to select candidates for manual testing, and also for automation testing after a few months.

The company has put forward the following criteria for the position of Manual QA:

• quality assurance (QA) engineer to work full-time 
• should know how to work with User Stories (Agile approach) without detailed descriptions or technical specifications
• English and russian speaking

The main tasks for this position were to write test cases and provide such types of testing manually:

• Manual testing
• Functional testing
• Usability testing
• System testing

There were no specific requirements for automation testing, but as a result of the consultation, a program language and framework for automation were determined and a candidate was chosen.

before

The application was under development after a complete update of the previous version. Manual and automation testing was not conducted. Unit testing was conducted by the developers.

implementation steps

1. Acquaintance with the project.

The tester should understand what user needs the application satisfies, and how the user can interact with the functionality. This is necessary to reproduce all possible and impossible user actions and make sure that the application fully addresses the needs. For this, a tester on a new project needs to familiarize himself with the available documentation, devote time to studying the application, input data, and meetings with developers and the product owner.

2. Creating test documentation.

Documentation on the project as a whole is always a guarantee of organization and understanding in the team. The same applies to test documentation. It is usually a good idea to start with a test strategy and plan. In this project, checklists were created for convenience and speed. After that, test cases and suites were written.

3. Determining the degree of quality to the design and functionality of the product.

After researching the product and creating the necessary documentation, a conclusion was made about compliance with the specified criteria and the quality of the application. All points were discussed with the team. After that, a further testing and development strategy was adopted.

4. Performing various types of testing with the functionality that was developed.

At first, it was testing of individual modules. Then was conducting testing of the interaction of modules. As a result of the conducted test detailed bug reports were written.

5. Further quality control.

After setting up the works, performing re-tests and regression testing were conducted every sprint (2 weeks). And also testing reports were provided to the project manager.

Automation testing was provided after a couple of months. After getting acquainted with the project, the strategy, environment, and means of testing were determined. Based on previously written test cases, automated end-to-end tests were created.

types of testing, tools, and programs

It was an interesting and voluminous project. Many different types of mobile application testing on iOS and Android systems were used on it.

As concerns of the object of testing:

• UI testing
• Functional testing
• Microservices testing

According to the level of testing performed Integration and System testing. Regression testing, Smoke testing, and Retests were conducted at the end of every sprint. 

Also, Installation testing, Localization testing, and Capability testing were performed.

Manual testing was very painstaking and careful. For UI/UX testing was used ShareX, Test UI plugins in Google Chrome, and Developer assistant. For reading errors on mobile devices, tools such as Xcode, iMazing were used.

Given that it is mobile applications that need to be tested, for automation testing, it was decided to use TypeScript with WebdriverIO. To connect and perform testing on devices were used Appium and BrowserStack. Test reports were provided by Allure Reporter.

features of the project

To ensure full functionality, the application required many microservices. For example, for payment in various ways, document scanning, and facial recognition.  All microservices had their own specifics and checklist for testing.

result

The customer's requirements were successfully met. The project is being supported.

During active cooperation, regression testing was performed at the end of 14 sprints, 1000+ bug reports were entered into the bug tracking system, and the application was successfully released.