Ashley Scopes opened SUREFIRE-2101 and commented

If I enable phrased test naming in config, and then write a test such as the following:

// Note no @DisplayName("...")
class SomeTest {
  void fooHasThreeCharacters() {
    assertThat(foo).hasSize(3);
  }
}

...then the console reports will contain a null name rather than something meaningful.

I am proposing that when this phrased name is unavailable, Surefire should fall back to the original test name that would have been provided if phrased naming was disabled. The reasoning behind this is that showing an unformatted class name is more useful to the developer reading Maven logs than just the phrase null.

!example-reproduction.png!

Affects: 3.0.0-M7

Attachments:

• example-reproduction.png (131.94 kB)

Remote Links:

• GitHub Pull Request #549
  
• GitHub Pull Request #587