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.
The old way
We maintain a set of spreadsheets with urls to test, instructions, and different scenarios that should be tested (browsers, resolutions, etc.) that we send out to testers. In our case we don't have a dedicated test team, but rather, different stakeholders chip in when the release cycle demands it. Most of our testers never use the