| |

Guidewire Performance Testing, 5 Reasons Why It Is Critical

Guidewire performance testing are critical to the success of every implementation. Typical testing verifies functionality but performance testing verifies the customer experience. Slow performance or strange results impact your brand by impacting your end customer, producers, claims adjusters, batch applications, even aggregators and other services. How many lost opportunities due to a slow quote?

  1. Load testing – simulating volume. Numerous circumstances can artificially inflate the traffic to your system for short periods of time. Environmental catastrophes result in massive claims, successful marketing campaigns can produce even more than expected opportunities, or opening a new state or country. Are you ready for these spikes in usage? What happens when you fail?

    By running load testing with involved business scenarios or increased user count, you can identify performance bottlenecks within your code or resources and thus reduce costs of failure and increase customer satisfaction.
  2. Stress testing – what happens under stress? You need to understand when you break and what happens when you break.  Running many different concurrent tests to the point of failure let you determine if that failure is realistic. For example, you need to support 1,000 concurrent users and verify you can. If you fail at 5,000 concurrent users, as long as you recover and provide a reasonable experience instead of the infamous spinner, you’ve addressed that concern.

  3. Run often, run early, run everything.  Running everything eliminates regression defects. Running early lets you identify design flaws.  Running often simplifies defect resolution because topics are still fresh in your team’s mind.  Without all three, you risk moving defects into production. Continuous Integration and Continuous Delivery addresses all the above points.

  4. API Load Testing – don’t lose opportunity. Current Guidewire implementation is a sophisticated application of interconnected services. You need to make sure the exposed API can handle the increased volume of requests. Are you sure your Aggregator API can handle 5,000 requests per minute? If not, you will lose opportunities.

  5. Advanced Analytics – monitor trends. We track every click, set, assert, and more; without additional code and without performance penalties. When combined with your CI/CD, these extensive metrics let you quickly detect trends over time thus providing a robust monitoring solution of your Guidewire application. Ensure SLA compliance!

Performance testing capabilities are powered by our active thread management for test execution. Watch a short video and see it in action!

Why Kimputing? We understand Guidewire intimately and use this knowledge to support your competitive advantage. CenterTest is Java-based, which provides flexibility and easy incorporation of additional requirements.

Do you have a special need beyond what’s already provided? Let us know and we will work with you to provide a tailored solution for your specific Guidewire implementation.

Arek Frankowski
Senior Software Architect

Watch or read our other posts at Kimputing Blogs. You’ll find everything from Automated testing to CenterTest, Guidewire knowledge to general interest. We’re trying to help share our knowledge from decades of experience.

Similar Posts