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.

On the evening of 12/31 I got the results from the team. They had tested every accessible page, compared it against the site map and screenshots, and made sure every link functioned, everything was accessible and graphics looked as good as they should. They also tested with Javascript off and with adblockers on. I verified all issues reported, standardized the reports and put it all together with a brief description of our testing methodology and delivered at about dawn of 1/1.

Asking employees to do this sort of work would be burdensome, particularly during the holidays, but it's why we offer web quality assurance testing services. Quick turnaround, short notice, little documentation and intensive testing are how we describe the QA work we do.