Testing and going live

Guidewire is on a mission to let insurance frontend developers unlock a wave of innovations with Jutro Digital Platform (JDP). Implementing an efficient application development workflow is the ultimate goal. This will allow insurance companies to go from idea to market solution in the least amount of time.

The application development workflow introduced by JDP requires two types of optimizations:

• Inner-loop (zero to dev): Speed up time taken to push code changes from local to development environments.

• Outer-loop (dev to prod): Speed up time taken to move changes from development to production environments.

To achieve this, Jutro provides tools and frameworks to streamline the inner loop. Jutro also introduces automation capabilities to build and release Jutro apps. In other words, Jutro helps insurance frontend teams to optimize the outer loop.

note

Guidewire customers have full control over the Star Systems and Planets necessary to meet their business needs. The proposed Jutro app development workflow suggests the following stages (or Star Systems):

• NPE-Development: Non-Production Environments (Development)
• NPE-PreProduction: Non-Production Environments (PreProduction)
• PE: Production Environment

Jutro Application Development Workflow

Jutro introduces an application development workflow that involves the following steps:

1. Code: Guidewire uses Git as the single source of truth for Jutro app code and version management. During development (or inner loop), Jutro introduces the idea of branch per environment. This allows you to deploy your branches in different target development environments. This caters to the following use cases:

   • Deploy various Jutro app branches pointing to different InsuranceSuite instances.
   • Quickly switch the target InsuranceSuite instance for a Jutro app. Do this by redeploying the application on a particular development environment.

2. Build and Test: The Jutro app build process triggers after you commit and push a change to any Jutro app branch. This generates a new Jutro app bundle that is ready to for deployment. By design, the proposed workflow always takes the latest Jutro app build. This also preserves using Git as the single source of truth.

   Build tests

   The build process executes unit and integration tests for the Jutro app. This uses your testing framework of choice for React-based applications. This includes jest and react-testing-library. You can find more information in the build and deploy a Jutro app documentation

3. Deploy and Test: With Jutro Web Apps, you have full control of how, when, and what Jutro apps to deploy on Guidewire Cloud. You can specify concrete integrations with InsuranceSuite instances. You can do this for every Jutro app branch in the development stage. Jutro's management console allows you to perform the following activities to achieve this:

   • Launch a new deployment for the latest build of a Jutro app branch on a particular development environment.
   • Redeploy the latest build of a Jutro app branch on the same or a different development environment.
   • Undeploy a particular Jutro app branch deployment from a development environment.

4. Promote: Guidewire recommends merging your application changes to the main branch. Do this once you have finished and tested your application changes. You should have an active deployment for that branch on a particular development environment. Once tested and accepted, you are ready to trigger the promotion process to the next stage.