Test names usually tend to become very long and difficult to read. JUnit5 allows us to set custom test display names, different from the test method names.
Testing
Testing in agile software development is crucial in assuring quality is delivered. Well defined testing strategies and high-level of automation make continuous delivery a reality.
Testing for exceptions in JUnit has never been a very straightforward thing. I've often seen it mangled, misused or not well executed, especially in JUnit 4.
Before JUnit 5 running tests in parallel was not easy. Luckily, now we have JUnit 5, and it has the possibility of running tests in parallel out of the box.
Although not a novelty concept, dynamic tests in the current form were introduced in JUnit 5. The main point of dynamic tests is to demonstrate that users can can generate tests dynamically, at runtime.