It should be noted that testing consists of such a wide array of tasks that it's often as hard to find the right people than it is to identify the right type of testing they should perform.

While performance and load testing on Healthcare.gov should be obvious tasks we get into murky territory when asking questions like: Does the UI need to be tested more than the APIs that power it? Will the value of automated end-to-end testing be deprecated after a UI refresh takes place? (Will there be a UI refresh?) How much time should be put into scalable UI tests? Are automated smoke tests enough?

I could go on, but the question I'd like answered is what did the actual testing plan consist of?