Site Testing Methodology?

Please forgive me for raising one of the few subjects more sensitive in software development than documentation. That would be system level testing. So, I'm sorry if this question makes anyone uneasy and wanting to change the subject! I'm using DB_DataObject, so my object methods contain much of the application logic and should be pretty easy to exercise with PHPUnit. Fine. That's the unit level. Unit testing is easy to think about and easy to implement in a nice neat package. However, at the system (gui) level, it starts to get messy. There is template and form I/O above the data object level. So, an external program is required that will do GET and POST and parse the resulting HTML from the server and then throw some hand-written assertions against the output. It can also connect to an SQL server and do setup and cleanup of test requirements. See awbot.sourceforge.net for a Perl example of such a thing. Is such a bot the best solution for a Pear project? Is there better open source site tester? Has anyone built one in Pear for Pear? I'm hoping such a thing would be of a white-box nature in that it is aware of the data model, form and template levels of the Pear site in order to semi-auto-generate tests. What is everyone else doing? Thanks for any discussion. -- Mitchell Perilstein mitch at enetis dot net www.enetis.net/~mitch