Building a Camel Case @DisplayNameGenerator For JUnit 5
I am loving the new JUnit 5 features and the @DisplayName annotation seemed like a great idea. However, it was a lot of work to write and keep updated - especially when you like to write descriptive test method names. It just seemed like unnecessary duplication. With the latest JUnit 5.4 release and the new @DisplayNameGenerator API all of that will change.
I think it is fair to say that JUnit has been my go to unit testing framework for quite a while. I have used TestNG on some pretty major projects where it was already in use (and it has some awesome features) but if I am building something from scratch, I will most likely reach for the JUnit maven dependencies.
