The meetings of the Hamburg Drupal User Group are developing rapidly. Yesterday we had the incredible number of 37 participants. At the first meeting after the Drupaletics in Cologne, we had 14 participants.
Subsequently, 19, yesterday 37. Does the development follow the law similar to the Fibonacci series of numbers? Will the room the next time be sufficient? Madness!
According to Stephan Luckow yesterday was the nationwide user group record.

As I've said elsewhere, I am no friend of relative complexity, as dictated by third-party Basic-CSS.

Tests are an important issue in modern software development. With Drupal, we have the ability to use Simple Test. It's become standard for Drupal 7, and is used to test the entire Drupal Core, plus a few of the modules. The whole thing is managed by Boombatower, who's Blog incidentally, provides a huge amount of interesting information on the subject of testing.
Simple Test is a mixture of Web Crawler and DOM Parser with some highly useful functions. We use a collection of objects in a completely empty Drupal, configure these as we need them, load the sites, then see whether the data has been transmitted in the way we intended.
What we have in Simple Test is a 'deterministic' test. From the same sequence of logical steps, we'll always obtain the same answers. When we don't, we know somethings' gone wrong.

So then, how exactly do I go about creating a test, what can be tested, and what are the limitations?

The Drupal module Views possesses an API for embedding plug-ins.