A problem I routinely run into managing a major government agency's public website is Quality Assurance Testing (QAT). QAT is complicated to set up, tedious to track, and always seems to consume more energy and time than it deserves. For example, for a site with 10's of thousands of pages, several discrete "applications", and a dozen integrations with outside systems, the test plan runs into hundreds of individual lines.