Tomek Kaczanowski works as a senior Java developer and technical team lead. He is an experienced Java developer, focused on code quality, testing and automation.
Test infected TDD enthusiast, open-source proponent, agile worshipper. Strong inclination towards sharing his knowledge. Author of the "Practical Unit Testing with TestNG and Mockito" book, blogger at http://kaczanowscy.pl/tomek. Occasional article writer and conference speaker.
Writing tests looks simple - every kid could write few lines of JUnit code. :) Writing valuable tests is more challenging. Everyone have seen (or written himself!) tests, which are hard to understand, hard to maintain, and do not verify anything really important (or maybe they do, but it is too hard to deduce)! Some tests are simply a burden. I want to present few examples of bad tests and show the ways of improving them. Along the way, I plan to discuss some general issues related to writing tests, present few tools (that are not so commonly used) and discuss some additional stuff like the code-review of tests. All in the name of writing good tests.