I have been using Guidewire Gosu for 12 years, and little did I know about the expense of using a simple dot until I invested time and looked deeper. In this blog, we will break down what happens when we use the brief dot notation. So whether developing or maintenance is on your mind, strap in and get some popcorn because here we go.
In another blog, we covered some basics on the query language and how to make it perform better. However, if you are like me, you want to understand more internals to be better informed when making decisions. This blog takes a deep dive into the inner workings of queries and caches used by Guidewire (GW). Let’s compare a set of Guidewire queries and the resulting SQL as a starting point.
In Guidewire PolicyCenter, one of the core objects is PolicyPeriod. It is not uncommon to see someone try to extend the PolicyPeriod with the rationale, "This change seems more policy related and does not fit on the line or one of its sub objects.”
In version 10+, Guidewire has added a new intrinsic datatype to Gosu which allows objects to be created and used very much like javascript. The functionality, while very nice, is not as complete as it is in javascript but may be in future releases.
In OO parlance we are very used to inheritance, polymorphism and subtypes. These let us create objects which share common properties and methods that we can override within the different classes. Since these objects come from the same base object, they can further be cast from one type to another, as long as the parent type is the same.
Coverage Analytics is a part of the Guidewire automated testing framework - CenterTest. It is based on the data captured during the testing process and provides a deep insight into the effectiveness of your testing. Finally know how much of your changes have been covered with tests.
Guidewire test automation,
