Sorry freakinname readers; today's a documentation/planning day, so I'm squirreling away links like mad. So without further ado, here's another:

Extreme Rules, Code the Unit Test First

Creating a unit test helps a developer to really consider what needs to be done. Requirements are nailed down firmly by tests. There can be no misunderstanding a specification written in the form of executable code.

Course I've always wondered how to write unit tests for GUIs. It's awfully easy to write a test for server-side code, but what about when a user's involved? Well, dummy, that's easy, as explained here:

>[Issue with unit testing number] 2)There is a lot of user input reqired.

For the past year we have developed unit-testing approaches for user interfaces. Basically, the 'button-click' (gui element) action is invoked by the unit-test which then makes sure that the appropriate results occur. We assume that system testing will make sure that the right actions occur when the user presses the gui button.