I have not come across as anything called Test  Planning.
Please correct me if I am incorrect

Test plan consists of the following fielss
1.Overview
2.Scope
3.Assumptions
4.Features to be Tested
5.Exceptions
6.Resources
7.Environmnnt
8.Scenarios
9.Entrance Criteria
10.Exit Criteria 

both are same 
Test plan is a document that gives important information 
about the projects in terms of schedule, resources , 
time ,milestones ,risks , budget, scope , objectives of the 
projec t

with Testplan  we can know what to test ,when to test, who 
test

Test Plan is the document which contains the information 
like, what to do, when to do and how to do.

Test Plan: Test plan is also called as test matrix. Test
plan is documents where it used to maintain the testing
processes. Test plan is a documents through which we can
follow of testing cycle. 
Test Plan consist of
1.Test plan Id.
2.Test Plan Objective.
3.Scope.
4.Feature to be tested/Feature not to be Tested.
5.Approaches
6.Suspension/Resumption Criteria.
7.Start/Exit Criteria.
8.S/w risk analysis.
9.Environment need.
10.Data deliverable.
11.Test Strategy.
12.Testing Task.
13.Risk.
14.Staffing and training need.
15.Schedule.
16.Responsibilities.
17.Approved.

So On.......... 
Test Planning:
Test planning is the pre-defined schedule where a Tester/QA
engineer should decide to testing the application and
maintaining some documents as required based on application
 and client.  


For details of any topic mail me to : mrrabi.it@gmail.com

A test plan is a document that describes the objectives, 
scope, approach, and focus of a software testing effort.The 
following are the items that might be included in a test 
plan, depending on the particular project: 

•Identification of software including version/release 
numbers 
•Revision history of document including authors, dates, 
approvals 
•Table of Contents 
•Purpose of document, intended audience 
•Objective of testing effort 
•Software product overview 
•Relevant related document list, such as requirements, 
design documents, other test plans, etc. 
•Relevant standards or legal requirements 
•Traceability requirements 
•Relevant naming conventions and identifier conventions 
•Overall software project organization and 
personnel/contact-info/responsibilties 
•Test organization and personnel/contact-
info/responsibilities 
•Assumptions and dependencies 
•Project risk analysis 
•Testing priorities and focus 
•Scope and limitations of testing 
•Test outline - a decomposition of the test approach by 
test type, feature, functionality, process, system, module, 
etc. as applicable 
•Outline of data input equivalence classes, boundary value 
analysis, error classes 
•Test environment - hardware, operating systems, other 
required software, data configurations, interfaces to other 
systems 
•Test environment validity analysis - differences between 
the test and production systems and their impact on test 
validity. 
•Test environment setup and configuration issues 
•Software CM processes 
•Test data setup requirements 
•Database setup requirements 
•Outline of system-logging/error-logging/other 
capabilities, and tools such as screen capture software, 
that will be used to help describe and report bugs 
•Test automation - justification and overview 
•Test tools to be used, including versions, patches, etc. 
•Test script/test code maintenance processes and version 
control 
•Problem tracking and resolution - tools and processes 
•Project test metrics to be used 
•Reporting requirements and testing deliverables 
•Software entrance and exit criteria 
•Initial sanity testing period and criteria 
•Test suspension and restart criteria 
•Personnel allocation 
•Personnel pre-training needs 
•Test site/location 
•Others	

Whereas Test Planning is the process of creating and 
maintaining a test plan and is the process of thinking 
about the activities required to create a desired future on 
some scale. It is a formal procedures or an endeavor used 
for the creation of documents, diagrams, objectives to met, 
strategy to be followed or meetings to discuss the 
important issues to be addressed.

I think now the concept has been cleared.
Vimal (Test Engineer)