CenterTest Generators
Generic test automation tools break constantly because they're built on rendered HTML that changes with every Guidewire update.
CenterTest Generators read your actual Guidewire source code and produce test framework assets that mirror your specific configuration. When Guidewire changes, you regenerate in minutes and your tests adapt automatically.
CenterTest Generators parse PCF files, type list definitions, and product model configurations directly from your Guidewire source code repository.
The generation process produces several categories of strongly-typed test assets, including:
Page Object Models (POMs):
Widget references for all PCF pages across PolicyCenter, BillingCenter, ClaimCenter, and ContactManager. Each widget is represented by its correct type (WidgetInput, WidgetSelect, WidgetDatePicker, WidgetShuttleList, etc.), enabling IDE autocomplete and compile-time validation.
Unlike generic page objects built from HTML inspection, CenterTest POMs understand Guidewire's widget behaviors: asynchronous loading, wizard step validation, shuttle list interactions, and modal dialog handling work automatically.
Type Lists:
Java classes replace hardcoded strings with compile-time validated type list values. Instead of typing "Draft" and hoping it matches at runtime, you use "PolicyPeriodStatus.Draft" and the compiler catches typos before execution. "Draft" is still allowed as this supports DDT and negative testing.
Product Model:
Typed accessor methods for coverages, conditions, exclusions, and modifiers across all configured lines of business. These objects reflect your specific product configuration, not generic Guidewire defaults.
Helper Utilities:
Common utilities to simplify test automation. For example, data sharing utilities that facilitate communication across test execution contexts, enabling scenarios to pass policy numbers, account names, and other test-generated data between reusables and across Centers.
Generation completes in minutes, and your team can even automate regeneration through CI/CD pipelines to ensure test assets remain synchronized with development changes.
The generators require read-only access to your Guidewire source code and operate entirely within your environment. Source code never leaves your infrastructure.
Self-Healing
Self-Healing operates through the regeneration architecture. When Guidewire changes occur, Centertest regenerates framework assets from your updated source code. The abstraction architecture absorbs locator changes, widget type modifications, DOM structure updates, and version-specific rendering differences so impacted scenarios continue functioning without manual refactoring.
For example, a standard XPath locator for a driver’s first name looks like this:
driver.findElement(By.xpath("//input[@id='SubmissionWizard:LOBWizardStepGroup:LineWizardStepSet:PADriversScreen:PADriversPanelSet:DriversListDetailPanel:DriverDetails:FirstName']"))This structure is brittle, and difficult to read and understand. The CenterTest accessor and associated setter looks like this:
page.getFirstName().set("John")This structure can be understood by anyone and remains stable because it references the logical widget definition from the PCF, not the rendered HTML output.
Learn more by exploring our FAQ below, or schedule a consultation to talk to one of Kimputing's test automation specialists.