Ever heard the saying, “if you fail to plan, you're planning to fail?” Surely the sage who first turned this phrase was speaking of implementing a sound quality 
assurance program. In order to test a product, software or a website, you have to have a plan in place. First, identify the problem you are trying to solve. Second, picture what success looks like. Once you know where you are and where you need to be, the next step is to outline a testing strategy to help you accomplish your goal.
Within your plan you will want to include the testing strategy, identify key areas that need the most attention, testing environment – dev or staging, supporting documentation such as functional specs, traceability matrixes, comps or copy decks. A large part and very important part of your plan will be the QA test cases. These can be as informal as a checklist of things to test or as detailed as summarizing each test scenario, test data to apply, expected behavior, bug description and priority and any comments about the test. The benefits of creating test cases allows the QA specialist to formally track and document each step of the test they perform noting pass or fail, and log discovered defects. One of the biggest benefits is you are less likely to miss testing something, and you can always refer back to your documentation if anything blows up.
Now that you have your test cases developed as part of the plan, it should also include a communication and distribution process for handling bugs. It could be as simple as entering bugs into a bug-tracking system or manually entering them into a defect log.
Okay so I have provided all the parts of a comprehensive QA plan, which includes a testing strategy, an end goal, testing support documents, test cases and bug management. What are you waiting for? Go test.