Summary of best practices

To minimize upgrade conflicts, Guidewire recommends that you avoid making modifications to the base configuration Behavior Testing Framework files. Instead, add your testing extensions to your own files. Exceptions to this recommendation include the following files, which are singleton files and present minimal effort when resolving upgrade conflicts:

• ContextFactory.gs
• ContextFactoryImpl.gs
• PCRemoteSmoketestHelperModule.gs

To ensure that your customizations do not create any upgrade conflicts, Guidewire recommends the following:

• End all file names with an _Ext suffix.
• Create context API interfaces in gw.cucumber.customer.context.api.<approach>. The name of <approach> identifies the technology used in the implementations, such as smoketest or rest.
• Create context API impls in gw.cucumber.customer.context.impl.
• For you initial scenario, implement the interface methods so that they throw an UnsupportedOperationException. Once you have confirmed that the scenario fails and throw this exception, you can replace impl methods with actual code as needed.