Evaluate the usability of the base configuration scenarios

Some of the base configuration scenarios may be applicable to your implementation. You can use these scenarios to test product behavior without modification.

Other base configuration scenarios may not be applicable to your implementation exactly as coded. There are two possible reasons for this:

• The scenario will pass in your implementation, but its conditions are not rigorous enough to constitute a meaningful test.
• The scenario will fail in your implementation because the behavior to be tested has been altered in your implementation or the scenario’s data is not applicable.

Guidewire recommends the following for base configuration tests that are not applicable to your implementation:

• If the scenario will pass, but its conditions are not rigorous enough to constitute a meaningful test:
  • Keep the scenario test as is in the original file, as this minimizes work during upgrade.
  • Create a new scenario with sufficient rigor in a new file.
• If the scenario will fail, modify the original file and remove the scenario. This creates a more reliable environment for QA because all scenarios are ultimately expected to pass. Modifying the original file will cause a conflict during any future upgrade. Therefore, Guidewire recommends you also keep records of modifications made to base configuration scenarios so that future upgrades can rapidly identify the source of any conflict.