Inspections - InsuranceSuite Developer Fundamentals

Inspection

The process of enabling static analysis to enforce standards and detect anti-patterns

True

(True/False) Inspection results display in the Gosu editor as Info/Warning/Error highlighting

True

(True/False) Guidewire Studio Inspections come bundled into Guidewire Studio and are provided as part of the InsuranceSuite base products

Guidewire Studio Inspections

Inspections that come bundled with the base InsuranceSuite products

SurePath Plugin Inspections

Inspections that are available on the Guidewire community website and must be manually installed into Guidewire Studio

gwb inspect

The console command used to run a command line gradle inspection

inspectionResults

The folder name where command line gradle inspections store their results

True

(True/False) Inspections can be triggered manually via the UI in Guidewire Studio

False

(True/False) Inspections can only be run via the command line as a gradle task

True

(True/False) You should run inspections before a Git pull request is performed

True

(True/False) Inspections can be set up to run as background tasks to catch errors as code is entered into Studio

True

(True/False) The automated build process will run inspections automatically in the CI/CD pipeline

Static

(Static/Dynamic) Inspections are all about looking at and analyzing __________ code.

True

(True/False) Seeing red squiggly lines on your code is an example of an Inspection working.