![]() ![]() Now i am trying to upload the local copy from PC2 to PC3(teamServer). Created a new repository in a different machine(PC3). So we made a final copy of the scripts to local in a different machine(PC2). The team was able to roll out the new security measures with no user impact.We had issue with the team server installed machine(PC1). So, in less than the two-week budget allotment, full API and end-to-end performance testing were completed using NeoLoad with ease. “NeoLoad’s plug-and-play UI was so easy-to-use that we were able to train colleagues ourselves within a few days quickly,” according to the company’s Director of IT Services. They also realized what they defined as “wins” using crucial NeoLoad capabilities such as mobile and AWS testing. Over three weeks with a NeoLoad testing portfolio of >30 web and mobile applications and ~20 APIs, the company’s dedicated performance team completed its migration and met the delivery SLA. Updates can’t sustain the wait that legacy performance testing solutions require, and without visibility over possible service degradation, rollouts can be risky and costly. Security patches and improvements must be completed quickly and tested comprehensively, especially for a health services giant. Unable to fulfill the new testing requirement resulted in the need to seek an alternative testing provider. If time compression wasn’t hard enough, the testing days demanding higher load volumes grew infeasible with their legacy solution, LoadRunner. Delivering this quickly became an additional success metric. ![]() Specifically, scheduling and resource coordination had to accommodate a 7 p.m. ![]() This required the performance engineering team to deliver comparisons and new baselines on performance to ensure a smooth and successful rollout.Ĭorporate security regulation compliance required that the performance testing team also create separate timing windows during which all testing can/cannot be executed. Plus, we are able to provide stakeholders with the pass/fail results - or whatever information they need - using NeoLoad dashboards, very early in the lifecycle,” the director says.Ī new security initiative was introduced across all vital enterprise services and apps. “If there’s a problem in the code or there are infrastructure issues or an API is breaking because of some backend services, we are able to debug very fast. With the NeoLoad-Dynatrace integration, the company has the data from both its NeoLoad custom dashboards and from the Dynatrace monitoring. With NeoLoad, the company brought everything under one umbrella and kicked off testing as part of a Jenkins pipeline. The advantage of NeoLoad is that it is equally effective for different types of applications (web, packaged enterprise apps, etc.), different kinds of tests (unit testing, end-to-end testing), and different teams of various skill levels (expert performance testers, non-expert developers). So we wanted a standard tool that followed a standard approach. Some were using open source, others were using legacy tools that took hours to build and run tests. “But teams were using many different tools. They used automation to break down the silos by going to a self-service model where DevOps teams could do their own testing.Ĭontinuous testing was a critical element in the company’s automation journey, the director notes. The company went to smaller release cycles so they could test earlier and resolve issues faster. The QA team didn’t have enough time to test, and if they found a problem, developers didn’t have enough time to fix it,” says the company’s Director of Information Technology Services. Sharing knowledge between teams wasn’t happening, and collaboration with the business was limited. Especially around collaboration where so many teams are working in silos with their own set of tools and processes. “There have been ups and downs in implementing change. ![]()
0 Comments
Leave a Reply. |