During one of my conference talks I got an interesting question: "why do you prefer to test exceptions using catch-exception library instead of using ExpectedException Rule of JUnit?". This is a good question, so let me answer.

I have just returned from 33rd Degree 2013 conference. And I'm very happy I've been there!

Should you put comments in your tests code? Yes? No? Why?

My blog was quiet recently and for a good reason. The thing is that am working on a new book. Well, on two books, or maybe rather one and a half book. ;) Ok, here is the story.

Mutation testing - once a academic toy and today a new trend in testing. Let us hear what Henry Coles, author of the PIT Mutation Testing tool, has to say about its development.

Recently I've been struggling to make Maven execute two Tomcat instances (with different applications on different ports). I decided to put a solution here so you don't have to discover it by yourself.

Some time ago I was complaining about the stagnancy of JUnit. This project - even if used by the majority of Java developers - looked abandoned. No new releases, no activity on the mailing list, no updates on the website. However in recent weeks things started to look better. I would like to share with you some comments regarding JUnit current progress.

Sometimes when releasing your projects on Jenkins you will encounter this Maven error message:

You don't have a SNAPSHOT project in the reactor projects list

even if your pom.xml contains proper (x.y-SNAPSHOT) version.

The default support for parameterized tests is one of the greatest weaknesses of JUnit. Let us see how Zohhak can help.

The second day of JDays 2012 in Goteborg, Sweden. A lot of good talks!