Trepp LLC (DMGT Co.) Increased Automated Browser Test Coverage With LambdaTest

Cross browser automation wasn’t a part of the QA checklist

When Anish joined, he added additional QA rigor and process, in addition, to cross browser testing at Trepp that wasn’t there before. These changes and maturation of the process quickly resulted in benefits almost immediately.

With frequent changes, upgrades, and new features getting rolled out led to shorter sprints, which became a challenge to maintain the quality standards. It became pivotal to ensure that the UI of the Trepp CMBS web application suite works flawlessly in various browsers and operating systems, including legacy configurations.

Prior to using LambdaTest for testing, they were using a cloud infrastructure, including some real devices for testing. There were fundamental issues and challenges that their team was looking to overcome, which were proving to be a blocker to their pipeline while running the tests.

Anish envisioned the need to automate the QA workflow and incorporate cross browser automation for future sprints. Now comes the bigger decision for the Trepp team, either to consider the possibility of building in-house vs. cloud platforms. After considering all options, Trepp identified these challenges related to building an in-house grid:

• Heavy cost and Reliability involved in building device lab.
• Time-consuming and on-demand scalability issues.
• Dedicated DevOps team required to maintain device lab.
• Limitations to run parallel sessions at scale.

Consequently, Anish decided to move on to the cloud ecosystem and also have comprehensive end-to-end cross browser automation testing as a part of their process.

With the ability to scale and run tests remotely, cloud-based infrastructure became indispensable

With LambdaTest, the team was able to have a seamless execution of cross browser compatibility tests across multiple browsers, thereby cutting down on the execution time and cost.

As per Anish, a build that would usually take them three days to test was now being executed under a couple of hours.In sprint Feature test, integration testing and E2E regression tests at the end of each sprint cycle were becoming the bottlenecks to execute in parallel. Having LambdaTest now, QA team can work in parallel with scripts being executed on the LambdaTest cloud that further trimmed down the test execution time drastically.

One real time example is Trepp’s CBMS product that has thousands of data variable calculation based on assumptions, portfolios, scenarios, upload/download files, and comparing data between different files and environments:

• 2-3 days for 1 round of testing to a couple of hours.
• Can run multiple test cycles in a sprint .
• GitHub Action and GitHub Package registry for more automated CI/CD process.

Trepp’s QA team was now able to run their Selenium test automation scripts on an extensible and modular Selenium Grid. Since the SDETs were more proficient in Java, they preferred using TestNG and JUnit framework for unit testing while using Rest-Assured for API testing.

“As LambdaTest’s Selenium Grid was compatible with every test automation framework and language which is supported by Selenium, the transition was quick and smooth, and my team can now run Selenium automation using various Java frameworks,” said Anish.

• Node Js with React for Functional UI automation testing.
• JavaScript and Typescript for the front end.
• TestCafe for automation.

A resultant confidence boost due to fast and better insight into visual bugs

Now, a major part of Trepp’s QA goes through LambdaTest, where everything happens on the cloud without having the need to manage resources internally or requiring any DevOps support. The ability to run automated tests on a range of different browsers and operating systems was a huge bonus for Anish and his team.

With LambdaTest cross browser automation on the cloud, now Trepp can:

• Increase test coverage on multiple OS & Browser configurations.
• Maintain seamless user experience even on legacy configurations.
• Reduce test execution time to a couple of hours from three days by parallel testing.
• Better monitor integrated insights through automation logs and analytics.
• Cut down the time and cost of maintaining infrastructure/test farm.