> I wouldn't be too hasty, there, those controls are going to change over
> time, breaking both your scripts and your database records.
>
> I've built a number of these sorts of things, and I find that it is
> better to define sets of paths through the application that accomplish
> particular objectives, as opposed to testing widget-by-widget.

Chris has a good point. Furthermore, most modern browsers "fix" HTML,
by adding missing tags, etc. Testing that the HTML elements are correct
might be better done at the HTTP layer.

Hope that helps.

-Jonathan