What must the names of GUnit test classes end with?

GUnit test classes are conventionally required to end with "Test" to clearly identify them as test classes within the Guidewire framework. This naming convention not only aids in organization and readability of the codebase but also allows the testing framework to recognize and execute the test classes efficiently.

By adopting this convention, developers can easily distinguish testing classes from standard application classes, fostering better collaboration among team members. Following these naming conventions also helps ensure that the integration with testing tools and frameworks works smoothly, reducing the potential for confusion or oversight, particularly in larger codebases.

The other choices do not align with the established standards for GUnit testing class names. "TestMethod" and "UnitTest" could create confusion with specific testing methodologies or frameworks that do not correspond to Guidewire's conventions. "TestCase" also suggests a different context that may not fully encapsulate the purpose of a GUnit test class within this specific framework.