To easily see in test failures what went wrong we follow the naming convention:
UnitOfWorkUnderTest_Scenario_ExpectedBehavior
Which mimics the internal GWT structure.
UnitOfWorkUnderTest_Scenario_ExpectedBehavior
Which mimics the internal GWT structure.
@DisplayName("throws IllegalArgumentException when given bad data")
void badData() {given_someInput_someOtherInput_when_doX_then_thisThingHappen_thatThingHappen
which has the advantage to be optimised for reading. When I want to skim over the test class quickly I can simply look at the method names to get an idea on what the test is doing and if I want more details I can look further at it's implementation