Among the many things you need to check out with your Drupal site is it's RSS feeds. While RSS feeds might still be an unknown to many of the visitors to your site you can safely assume that will change sooner than later, and to those who know it, it's their way to monitor what's happening on your site on a daily basis.
Over the holiday season we got the opportunity to do some QA testing that epitomized the type of work our QA team is set up for. Development of a 100 page static site was going over schedule, and wouldn't be ready for QA until days before delivery was due - and delivery was January 2nd. We set up a plan and on 12/30 we got the URL to test and jumped in. We had a site map and some screen shots of what the site should look at. The client had not had the time to put together a testing plan or setup an issue tracker. Our team was to test against 4 operating system/browser combinations for a total of 64 hours of testing.
I often compare Quality Assurance (QA) testing to janitorial services - it's not high profile, can seem tedious to some, and in many cases could be done by outsiders (like us). The high profile work is the design, or maybe the programming of the functionality of a site. QA comes in usually at the tail end, and rarely has much communication with anyone doing anything that could be considered strategic. QA is similar in ways to doing a really big puzzle, or a stack of sudoku or crossword puzzles - the novelty can wear off quickly for many. It's painstaking, careful, organized work. Particularly for companies making websites QA is often best done by outsiders. The volume of work can fluctuate a lot, it can be hard to retain QA people and maintain a testing environment. And by using outsiders you get objectivity that you can't get from people working alongside those who made the site. A site should work however it's used, and if you know "too much" about a site, you may not try to use it in all of the ways it could be used. You can also use outsiders in ways that you wouldn't be comfortable using your own employees. Since QA is often last to the end of a project, and that time is most often eaten up by other work so that deadlines are looming, it's great to be able to test overnight. Asking your employees to stay overnight is bad for morale. Asking a company like InteractiveQA to test overnight doesn't surprise us, and we're happy to provide the service.