SQL Server DR Plan - Test Documentation
I recommend keeping the document very simple and short so it is something that is easy to read, easily understood by people that are not experts in database technology and easy to update.

People have far better things to do than read long test plans, however the test plan should be detailed enough to be followed, its a tough process.

Based on this I believe the things that should be included in the test plan are:


Success Criteria for each tier (tier-1, tier-2,tier-3, etc)
Method of Testing for each of the Success Criteria 
preferably including links to scripts in source control and instructions on how to execute each test.
List each Server(s) covered in each of your tiers and therefore covered by each success criteria.
Glossary of any Key terms to remove Ambiguity (plain english explanation of Recovery Time objective, what tier-1 / tier-2 means, etc)
Date Last Modified
Create a team calendar event which is used to remind the team to revise the document each 3 / 6 months to verify the document still reflects the environment.
Scope Definition (In-Scope &amp; Out-Of-Scope)


Other things may come to mind, but simplicity I think is key.

The only other thing that pops in my mind is while you may be writing a test plan for the database, don't forget that a live database that can't be reached by applications still does not meet business continuity objectives; though it may satisfy a data protection need. Consider adding some minimal application testing to your plan or explicitly rule it out by mentioning what is In-Scope and what is Out-Of_Scope.