The speed at which they’re able to understand the product is impressive. Trigent delivers everything that’s asked of them each sprint. The team is excellent at getting up to speed with new technologies. They’re an organized team that gets the job done.
The client the first true-cloud, enterprise-grade SaaS Platform for Insurance that enables insurers to rapidly build products and experiences for their millennial customers. They can configure and create any type of insurance product, for any region, and distribute it any way that they choose. They have quickly grown to become a trusted partner to leading insurers in the U.S, enabling them to serve their policyholders better. The platform handles the end-to-end process of insurance product development, pricing, underwriting, risk assessment, policy issuance, premium payment, customer onboarding, claim management, and payments.
To maintain its disruptive leadership position in the market, the client undertook to upgrade its platform that would offer an integrated front end that dramatically simplified the experience for both online customers and their agents. The new front end interface needed to:
Additionally, the new platform was designed to allow the insurance policyholders to self-serve. Hence every feasible situation must undergo quality assurance and testing (QA and testing), especially for exceptions or extreme circumstances, to guarantee that all use cases function as expected. It was important that all permutations & combinations options are thoroughly validated.
To achieve the desired Customer Experience (CX), the client switched from using a very old version of React, Typescript, Gulp, and Bower to the latest version of React and Typescript, supported by Webpack and npm. As the new CX was designed to provide customers greater flexibility and choice, it also exponentially increased the business rules and data requirements that needed to be validated.
The client partnered with Trigent to augment and extend their QA capabilities, undertake functional testing and build the automated checks across the new platform. The testing team got involved in defining the test strategy, the core elements of which were:
The automation team focused on the component integration and the end-to-end business functional tests parts of the test pyramid. Scenarios to automate were chosen to maximize coverage in areas of risk and business criticality. The API integration test cases were run at every pull request in the local development branch, periodically, in the main development branch and whenever a release was undertaken (usually weekly). API tests were integrated into the CI/CD pipeline and controlled through Jenkins jobs. UI tests, that covered critical business functionality, were to be run twice daily to check for regressions on the development branch and against release candidates on different test environments.
Trigent’s AutoMATE framework formed the basis and jump-started the framework development process, thus saving time, in an already time-crunched project. The enhanced framework enabled:
Achieved automation of 90% of the test scenarios across high risk and business-critical scenarios.
The entire CI/CD pipeline was set up so that the checks covered: