Best practices for creating step class files

To minimize upgrade conflicts, Guidewire recommends that you avoid making modifications to the base configuration step classes. Instead, add testing extensions to your own files.

The base configuration step class files are stored in gtest/gw/cucumber/steps.

Guidewire recommends storing all of the custom step class files, API files, and impl files in a single directory, such as gtest/gw/cucumber/customer, with the following subdirectories:

• context/api
• context/impl
• steps

You can use subdirectories in gtest/gw/cucumber/customer/steps to organize step class files. There are no technical restrictions for how to group step class files together. A feature can use any step method, regardless of the location of the step class that defines it. And, a step class can call implementation code from any impl file. Therefore, group files together in a way that makes the most sense to the business.

Guidewire recommends adding an _Ext suffix to all new files, including step class files.