The Test Plan is an overview of what you intend to test, how you plan to do it, what resources you need, how long it will take and other important issues. Depending on the size and complexity of your project, you may decide on separate Test Plans to cover Functional Tests, Performance Tests and other types of testing, or you may decide to use a single Test Plan to cover all your testing. If your project is very large and involves many people, separate Test Plans can make management of the project easier.

TALC Test Lead helps you to develop a complete test plan by providing a structured set of separate but related items which your test plan needs to cover. The "Demo1" example plan is provided to assist you, and is based on the IEEE 829 standard.

The Test Plan is a high level document, and is not intended to contain details of each test that you plan to run. That comes later. It is a management document that defines the scope of what you intend to do, and can be understood by all. It is used to manage and control the testing process. It is also a working document that you will almost certainly want to revise and update many times before testing is finished.

Section 3 of the Test Plan is titled "Features to be tested". Each entry in this section is linked directly to a folder or component in the Application Model. This linking, and other linkages which will be established later, is used to provide coverage reports that highlight application functions that have not been included in your Test Plans, Test Designs and Test Cases.