There are several benefits to having an automation solution that can be gained – from expanding test coverage, increasing frequency of execution, reducing manual testing resources etc. In our experience,  100% of Guidewire customers want to implement automation in their testing practice and 90% of them have attempted to incorporate automation into projects by either purchasing a licensed tool or acquiring a team to work with open source tools.

 Yet, what is surprising is that less than 10% of customers have truly been successful in building a robust automation solution over time. And even in these cases, it has taken them years of investment to reach a point where automation has become valuable.

 Testing is challenging and there are some major pain points associated with implementing automation with Guidewire:

  • Licensed tools get very expensive very quickly based on the licensing model and growing team size

  • Licensed tools that work great with other applications, crash and burn when exposed to the Guidewire platform

  • Several additional tools are suddenly required to build necessary coverage in addition to the primary functional test tool

  • Open source tools require a very high level of technical expertise to implement

  • There never seems to be a stable product to start the automation effort

  • Teams struggle with inflated maintenance overhead

 There are several others in addition to the above that are constrained by the tool and resources using them as well as the dynamic nature of Guidewire product platform.

However, the root cause of most issues, is the approach taken to test automation and the lack of proper tooling to implement the automation solution. One of the most common and widely made mistakes, is to determine automation scope as a percentage of manual testing effort. This is in direct conflict with the purpose of automation, which is to complement manual testing rather than duplicate it. Another common mistake is the belief that a single tool (licensed or otherwise) will be enough to accommodate all automation needs. It requires a significant amount of tools-evaluation to figure out the right mix of tools to develop high-yielding automation coverage.

Not having clear focus or boundaries for automation and manual testing leads to a huge amount of redundancy and dependency, which then directly affects the ROI. This is also why automation team always ends up playing catch up and never quite able to do so on fast moving Guidewire implementation efforts. Also, having the wrong set of tools directly results in wasted effort and creation of an automation test bed with very little value. Cynosure Testing Practice has developed the Cynosure Automation Testing Framework (CTAF) for the Guidewire InsuranceSuite with the purpose of jump-starting automation efforts of any scale and skill for our customers.

Jump-Start Guidewire Automation Testing with CTAF

Cynosure’s Testing Practice has put together a Guidewire Automation Testing Framework with the purpose of jump-starting automation efforts of any scale and skill for our customers.

Cynosure Test Automation Framework (CTAF) is a customizable data-driven framework developed using a combination of open source tools such as Selenium Web Driver, Maven, Apache POI, TestNG, Log4J, Java and Jenkins.

This is a packaged framework that comes with hundreds of built-in Custom widgets developed to handle special data entry/selection needs as some Policy Center Page field dropdown/lists and input fields don’t work with core selenium web driver methods. There are also built in End-to-End key product functionalities such as quote submission, policy issuance and invoicing to help implement these transactions very early on in the project. Also included are specialized utilities such as clock moves (date forwarding), Run batch processes and Event messages/Message Queues to assist with time based test scenarios.

CTAF Focus areas include but are not limited to the following:

  1. Continuous Integrations

  2. Regression Testing

  3. Combinatorial Testing involving large sets of data input and output

  4. Testing Guidewire Integrations

  5. Guidewire Upgrades

If you are reading this blog after your Guidewire solution has been implemented or if you are having challenges with your implementation, discuss the possibility of automation leveraging CTAF, feel free to reach out to the Cynosure Testing Practice to learn more about Guidewire Automation Testing best practices and associated products and services available. Contact Puja Mukherjee – Cynosure’s Director of Quality Assurance at and we will be happy to assist you.

+ posts
1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)


Posted by Puja Mukherjee

Leave a reply

Your email address will not be published. Required fields are marked *