Long time ago I got attracted to mutation testing (http://en.wikipedia.org/wiki/Mutation_testing). Alas, at that time all the Java mutation testing tools were useless: abandoned and forgotten long time ago. Lately I discovered a new tool - PIT Mutation Testing (http://pitest.org/) - which is actively developed. So I gave it a try. A very limited try (but that is only the beginning!).

Summary on what happened in JVM (Java, Groovy, Scala) developers testing world in December 2011. News from JUnit, TestNG, Mockito, Selenium, Arquillian, mutation testing and many more. Also links to some good articles and blog posts. Enjoy!

Summary on what happened in JVM (Java, Groovy, Scala) developers testing world in November 2011. EasyMock 3.1, JUnit Params 0.3, TestNG users survey, database testing tips and many more goodies. Enjoy!

Results of online survey on TestNG (Q4 2011). Let us learn why and how we use it!

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

One day I started to experiment with visualization of test dependencies. I thought that maybe Graphviz can help to provide some nice diagrams that would help me see instantly what went wrong, and why some tests are skipped. In this post I present my achievements so far.

Tests executed by hand can end up with plethora of results ranging from "*#$& exception!!" to "it works... and this exception has always been there". In case of automated tests things look different. There are only few possible outcomes. Let us take a closer look at them.

Oldest developers can't recall the times when TestNG introduced timeout constraints for tests methods (invocationTimeOut parameter of @Test annotation). The current beta of TestNG allows to set timeouts also for configuration methods.

If you use Eclipse & TestNG you might be interested in these two simple code templates that will help you to create DataProviders.