Many of our customers have accumulated large existing testing investments on their own infrastructure. As they migrate to Guidewire Cloud Platform, they have asked us to help retain their investments and accelerate their cloud migrations momentum and adoption. We want to answers those needs by assisting customers in their transition to the cloud by giving them an ability to integrate their tests results with CI/CD pipeline for InsuranceSuite applications.
With the upcoming addition to the Guidewire Cloud Console tooling offering called Quality Gates, Guidewire provides a standardized flow to enable approved third-party testing frameworks and a way to propagate the execution results into Guidewire Cloud Platform for quality gating. Customers can add the execution results directly in the Guidewire CI/CD pipeline to enhance developer experience, provide better transparency, and reduce the time and resources needed to identify and fix issues.
What are Quality Gates?
By quality gate, we mean a specific, pre-configured criterion that must be fulfilled before an artifact can pass a certain CI/CD step.
Currently, there are two stages that will be supported:
| Stage | What operation will it impact? |
| Pre-merge | Merging pull request |
| Pre-promotion | Promoting build to a higher planet class |
Quality gates can be split into two different types – default and custom. Guidewire will provide default quality gates as part of the Guidewire Cloud Console CI/CD offering. Custom quality gates are dedicated to reflect third-party testing tooling owned by Guidewire customers outside Guidewire Cloud Platform.
The quality gates framework provides a diversified set of APIs that allow you to perform maintenance operations on quality gates, check their status, and send testing results.
How do custom quality gates work?
Custom quality gates that enable you to bring your own testing tool into InsuranceSuite CI/CD pipeline are split into three parts:
- Notifications – an option to configure a callback to a given URL in response to a particular event in the Guidewire Cloud Platform CI/CD pipeline for InsuranceSuite applications.
- Gating mechanism – an option to prevent a commit from being merged or a build from being promoted to a higher-level environment based on configured criteria (for example, the outcome of external tests).
- API to propagate test results – a set of standardized APIs implemented in Guidewire Cloud Console microservices that enable users to propagate the pass/fail result for a specific quality gate.
How can you integrate your own testing with Guidewire Cloud Console via the custom quality gates framework?
In order to integrate your testing with Guidewire Cloud Console using a custom quality gates framework, you will need to set up your quality gates first. It is a quick and simple process that can be done through the GCC UI or API. During quality gate configuration, you will need to provide information about your tests. This will give you better transparency and visibility into your testing process.
Test results can be programmatically provided to the Guidewire Cloud Console using APIs. You can send these results in the form of a “verification,” which is a logical object that contains details about your test run. Depending on the quality gate stage, results can be viewed in Bitbucket or the Build Promotion UI. Additionally, you can use APIs to programmatically check the status of quality gates.
In order to fully automate the process, you can leverage CI/CD events, a new addition to AppEvents Webhooks. These notifications can be used as triggers to initiate tests with third-party testing frameworks. Currently, the following notifications are available:
- PullRequestOpenedEvent,
- PullRequestUpdatedEvent,
- RepositoryChangedEvent,
- IsAppDeployedEvent.
By combining the three components, you can create a fully automated “bring your own testing” solution. This solution will automatically initiate your tests based on the GCC CI/CD pipeline, and send the results back to GCC, provides you with better transparency and visibility into your testing process, and reducing time and resources required to identify and resolve issues.
What is the future?
The initiative is currently in the Early Access program. The scope of the program is limited to custom quality gates. We plan to release the feature globally with the addition of default quality gates in the summer of 2024, as part of the Kufri release.
Looking ahead, we have several exciting features in the pipeline. We aim to extend the scope of quality gates to additional applications (e.g. EnterpriseEngage). In addition, we plan to introduce additional notification types, auditing features and additional default quality gates including manual signoffs. The roadmap for the initiative is flexible and regularly updated based on customer feedback.
Want to Learn More?
I hope you’ve found this sneak peek into the incoming Bring Your Own Testing feature helpful.
The feature is available in Early Access for Guidewire customers. To request more information about our Early Access program for Bring Your Own Testing, please contact eaprogram@guidewire.com.
If you want to learn more about the features and functionalities of GCC, you can also check out Guidewire Cloud Console documentation (login required).
About the Author
Krzysztof Szczurek
Product Manager