Testing software whilst ongoing development seems to be a boring job containing a lot of reoccurring tasks. As a reaction on all this effects we need to add more testing. So what do we do? We use a person to click through the application, using its features as he or she thinks they are intended to use.
In the end we need another expert in the team for a boring reoccurring task, finding bugs that are easy to find and most times, simple to resolve. Did i say simple task, reoccurring? Why not use a Software for the click-around testing in our application to check if it still does what it needs to do ?
They step through the process of creating the test (no code) and show how to store them in CVS (as well as talk about a few "dirty tricks" they found out along the way).