GUIDEWIRE BEST PRACTICES EXAM NEWEST
ACTUAL EXAM COMPLETE 100 QUESTIONS AND
CORRECT DETAILED ANSWERS (VERIFIED
ANSWERS) |ALREADY GRADED A+||LATEST EXAM!!
Post On Change and Client Reflection Best Practices
Reflection - ANSWER-Involves both a listening and a
triggering widget (there can be more than one of each)
Define on listening widget from Reflection tab
Reflect changes on triggering widget(s)
Can set these properties on listening widget: Available,
Custom, InputMask, and ValueRange
Editable and Visible CANNOT be changed
Use with ListViews
GUnit Testing - A GUnit is - ANSWER-Guidewire unit
testing framework, used to configure and run repeatable
tests of Gosu code
GUnit Testing - GUnits 3 Facts - ANSWER-Available in
Studio and can be run from Studio
Can be automated as part of Continuous Integration
Cannot test the User Interface or Gosu Rules
,2|Page
GUnit Testing - Test Classes - ANSWER-Names must end
with Test
Extend gw.api.test.XXServerTestClassBase or
gw.api.test.XXUnitTestClassBase
Can include beforeMethod/afterMethod methods that run
before or after each test method is invoked
Can include beforeClass/afterClass methods that run as
test class is loaded or after all tests are executed
Are best organized in packages based on testing needs
Can be created to be reused for repeated functions or
data generation
GUnit Testing - Test Methods - ANSWER-Names must be
lower camel case, have names that start with test, and
describe the test being executed
Set up test data using entity builders and variables
Test and verify results using assert statements
Include annotations (optional)
GUnit Testing - Test annotations are - ANSWER-strings
that begin with @ and provide metadata about a Gosu
element
Example:
,3|Page
uses gw.xml.ws.annotation.WsiWebService
@WsiWebService()
GUnit Testing - There are two types of test annotations -
ANSWER-Server runtime annotations appear before the
class definition and indicate how the test
interacts with the Guidewire server
Environmental annotations provide additional test
functionality and override default system behavior
GUnit Testing - For code usability you should create -
ANSWER-Test helper classes or functions
GUnit Testing - When executing a GUnit test, do so by -
ANSWER-Package or Class
GUnit Testing - 4 characteristics of effective unit tests are -
ANSWER-Readable - speeds up developer productivity
Accurate - predictable and repeatable
Fast - long-running tests slow development and are
abandoned
, 4|Page
Independent - can be reliably run in isolation from other
tests to identify root cause of a problem
Guidewire Profiler is used to - ANSWER-Investigate
performance problems in the production environment
Help find and diagnose problems with database queries,
rules, and other Gosu code
Detect problems early by developers
Guidewire Profiler
Web profiler can - ANSWER-Be used for core product user
interface performance analysis
Capture current user session in which web profiler
enabled
Capture one set of results from receipt of a request
through sending response while enabled
Save the web profile in user session (gone when user logs
out)
Track where time is spent on server:
Guidewire application code
Response time of calls to database, external services, and
so on