Add new DisplayNameGenerator ReplaceCamelCaseAndUnderscoreAndNumber

[FanJups]

This extension handles method names with CamelCase, underscore and numbers.

The aim is to simplify unit test display names. Instead of using this method annotation org.junit.jupiter.api.DisplayName on every method, we can just use this class annotation org.junit.jupiter.api.DisplayNameGeneration and use that method annotation if needed.

This generator follows 3 rules:

• Each uppercase letter is turned into its lowercase value prepended by space.
• Each underscore is turned into space. Words bounded by underscores or just starting with underscore are not transformed. Usually these words represent classes, variables...
• Each number is prepended by space.

Closes: #793
PR: #819

---

PR checklist

The following checklist shall help the PR's author, the reviewers and maintainers to ensure the quality of this project.
It is based on our contributors guidelines, especially the "writing code" section.
It shall help to check for completion of the listed points.
If a point does not apply to the given PR's changes, the corresponding entry can be simply marked as done.

Documentation (general)

• There is documentation (Javadoc and site documentation; added or updated)
• There is implementation information to describe why a non-obvious source code / solution got implemented
• Site documentation has its own .adoc file in the docs folder, e.g. docs/report-entries.adoc
• Site documentation in .adoc file references demo in src/demo/java instead of containing code blocks as text
• Only one sentence per line (especially in .adoc files)
• Javadoc uses formal style, while sites documentation may use informal style

Documentation (new extension)

• The docs/docs-nav.yml navigation has an entry for the new extension
• The package-info.java contains information about the new extension

Code (general)

• Code adheres to code style, naming conventions etc.
• Successful tests cover all changes
• There are checks which validate correct / false usage / configuration of a functionality and there are tests to verify those checks
• Tests use AssertJ or our own PioneerAssert (which are based on AssertJ)

Code (new package)

• The new package is exported in module-info.java
• The new package is also present in the tests
• The new package is opened for reflection to JUnit 5 in module-info.java
• The new package is listed in the contribution guide

Contributing

• A prepared commit message exists
• The list of contributions inside README.adoc mentions the new contribution (real name optional)

[Michael1993]

Personally, I'd prefer to review this when the build is passing - if you need help, let us know.

[FanJups]

Personally, I'd prefer to review this when the build is passing - if you need help, let us know.

Sure, thanks. I am trying to test @DisplayNameGeneration(ReplaceCamelCaseAndUnderscoreAndNumber.class) but my test failed.

That's why it's still in draft mode.

[FanJups]

Personally, I'd prefer to review this when the build is passing - if you need help, let us know.

Sure, thanks. I am trying to test @DisplayNameGeneration(ReplaceCamelCaseAndUnderscoreAndNumber.class) but my test failed.

That's why it's still in draft mode.

Maybe, its because the generator is not well configured. The first test is green but the 2nd one simulating a real scenario does not.

[FanJups]

Hi @Michael1993 , please are available these days for a call ?