Last week I visited my first conference ever, JEEConf 2016. I had no particular expectations but it turned out to be a blast!
A lot of things are happening right now: I’m writing a book, I’ll speak at conferences, you can hire me, and to top it off, I gave this blog a new look.
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.
There are a couple of things you should do to make code reviews successful. Chief among them, keep them brief, short, and focused. This is the story of how I fucked up on all these accounts and we still made it work.
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.
JUnit 4 came in a single artifact, blending all uses cases into one bundle. The JUnit 5 architecture promotes a better separation of concerns and provides a clear API for IDEs, build tools, etc. to work with.
Many people will tell you how great blogging is. But as most publicity-related aspects of life it has a dirty underbelly, so let me share some of the reasons why you might not want to start your own blog.
While not particularly hard, building Atom on Gentoo is a little elusive and poorly documented. Look here for enlightenment!
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!
A couple of days ago, the JUnit 5 Alpha version was released. See how to set it up so you can write tests and run them with your favorite IDE and build tool.