Thorough introduction to parameterized tests in JUnit 5: How to create them, how to name them, where to get the arguments from, and how to customize that.
You can tell that Java 9 draws near because the number of posts and talks about it skyrocketed in the recent months. I want to recommend existing talks and articles […]
The module system allows optional dependencies with the ‘requires static’ clause. Module required this way are accessible at compile time but can be absent at run time.
My first stab at exception handling in Java streams. Explores how to repackage checked exceptions so that they can be thrown without the compiler complaining about it.
The desire for the Elvis operator (null-safe member selection) as a killer feature for terse null-handling echoes through the Java community. It should never be introduced, though, and here’s why.
In the fourth issue of SitePoint’s Java Channel Newsletter I summarize the discussion of Scala’s presumable demise.
Reflection wants to break into all code; encapsulation wants to give modules a safe space. How can this stand off be resolved?
We recently learned about JUnit 5’s extension model in general. Let’s now have a detailed look at custom conditions, which allow us to flexibly disable test methods.
The JUnit 5 extension model enables detailed, flexible, and powerful additions to JUnit 5’s core features. For that it provides specific extension points and easy composition of annotations.
Get to know the basics of JUnit 5: the lifecycle; how to disable, nest, and name tests; and what’s new with Assertions and Assumptions. Let’s write some tests!