faster test cycles
default
lower AWS testing costs
default
apps migrated to NeoLoad, 100 test scripts
default
The leading global provider of legal and business information/analytics needed to solve two parallel performance testing–related problems with one solution. First, they wanted to automate performance testing into their CI/CD pipelines. The company’s existing legacy tool (LoadRunner) was not only expensive; it also hindered their ability to become more agile, reduce test cycles, and promote collaboration between Dev and QA teams. Second, the cost of AWS resources dedicated to testing had to be driven down.
The company’s information network contains over three petabytes of legal and news data, with 128 billion documents from 60,000 sources. Each day the service processes more than 40 million documents and 77 million public records, with more than 1 trillion connections across all content types. With the ever-increasing volume of online research (both number of global users and amount of content) and the company’s innovative powerful data visualization and predictive analytical tools, the company knew they needed to move to the cloud.
Their technology service partner, Cognizant, transitioned the company’s database services to an AWS cloud architecture and shut down their legacy mainframes and servers. With all applications hosted in the cloud, they utilized AWS Auto Scaling, which automatically increases the number of Elastic Compute Cloud (EC2) instances during higher subscriber activity and then lowers capacity when not needed.
However, the company was concerned about how they were using AWS resources for their performance testing. Either there was no capacity for controllers and load generators when needed, or the company was paying for “idle” resources that were not being used optimally (especially during non-testing hours).
Challenges