This is a review of "Selenium 1.0 Testing Tools: Beginner's Guide" book by David Burns (Packt Pub, 2010).

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.

This blog post is devoted to two unsung heroes of testing: SUT and DOC. Who are they and what is their role in unit, integration and end-to-end tests?

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.

Few notes on two approaches to testing. Some people seem to be more interested in verification, others aim for better design.

Automation is the key to successful testing. This post explains why other ways of software verification are a waste of time.

Few notes on how setting a high code coverage can do more harm than good.

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.

My 3 cents on self-shunt testing pattern.

If you are not familiar with this pattern please read the following:

1. The 'Self-Shunt' Unit Testing Pattern - original article by Michael Feathers,
2. Self-Shunt blog post by Paul.

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