Recently I've spent some time browsing the Net and learned about some new stuff ("new" meaning "new to me") that I would like to share with you. Let us have a look at HavaRunner, some nice TestNG reports, and TDD Katas.

The slides from my short talk about JUnit and TestNG on 18 April 2013, BrighTalks.

To view the presentation click here.

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've promised to publish the slides from my JDays 2012 presentation "Bad Tests, Good Tests", so here they are.

This post presents results of TestNG 2012 Users Survey.

Please fill in a short online survey on TestNG. Let us learn why and how we use it!

If we expect our tests to act as a documentation then we need to put some effort into their readability.

For unit tests a rule of thumb is to keep them independent from each other. It is not so bad if we introduce a dependency on purpose (and explicitly declare it e.g. using TestNG dependsOnMethod feature). A worse scenario is when we are not aware of the dependency ourselves. This can bring serious problems on our heads.

Recently I was happy to see some new ideas discussed on Mockito and TestNG mailing lists. It is always nice to see plans for improvement, especially in such mature and features-rich projects.

Slides from my GeeCON 2012 talk "Bad Tests, Good Tests" along with the links to the technologies mentioned there.