Our client is a market-leading risk management solutions provider based in the UK with a global reach, serving over 45,000 customers.

The company was dedicated to its mission of creating safer and better workplaces through the use of their knowledgeable teams and advanced technology. Their goal was ambitious, they aimed to protect five million workers in North America from workplace incidents by the year 2025. Encountering software quality challenges, they wanted to optimise their QA process and identify any potential weaknesses.

That’s when Zuci’s consulting specialists were approached to evaluate the quality of the company’s QA process, detect its shortcomings, audit the test automation framework, and come up with recommendations for improvement.

Zuci’s QA consultants were eager to take on the challenge and help the company achieve its goal of creating better workplaces.

As part of the assessment, our team carried out interviews and questioned the client’s QA team members and thoroughly analysed all QA artifacts: Code base, Cypress automation framework, Azure pipeline and QA processes.

A comprehensive report was created that includes all the results, suggestions for improvement, and a plan for implementing the proposals.
Zuci’s consultants defined some of the problem areas and submitted proposals including the following:

Test automation framework:
The client’s automation test suite was written in Cypress version 9.4.1, which was lacking some of the latest capabilities. The QA consultants suggested that the client migrate to Cypress version 10, as this would provide several benefits, including:

• The ability to integrate with the Cypress Dashboard for easier analytics
• Advanced debugging capabilities with the Command Console

• Easy integration with reporting tools such as the Mochawesome report and Allure report
• The ability to group test cases and run the grouped test cases
• The ability to add tags to test cases
• The integration of the Mochawesome report for easy analytics and analysis of test cases

The consultants also noted that the current test framework lacked localization support and recommended adding language-specific json files for testing multiple languages.

Additionally, they observed that the test framework was implemented in three levels (pages, resources, and functionals), which made understanding the test cases tedious. As a result, they recommended revamping the framework to adopt the page object model in two levels (pages and tests) for improved clarity.