WHAt is diff between test plan and test planning?
- 5 Answers
- 7883 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / divya nandana.b
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
| Is This Answer Correct ? | 2 Yes | 1 No |
Answer / rabi narayan
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
| Is This Answer Correct ? | 1 Yes | 0 No |
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
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / kiran
Test Plan is the document which contains the information
like, what to do, when to do and how to do.
| Is This Answer Correct ? | 1 Yes | 1 No |
Answer / vimal
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)
| Is This Answer Correct ? | 1 Yes | 1 No |
what is the diffn betn web based application and client server application
In cycle 1 we have 100 test cases out of which 95 test cases are PASS and 5 test cases are FAIL. So in cycle 2 how many test cases performed as a part of regression testing?
Write 5 test cases for UAT of internet Banking system
2 Answers Infosys, Zycus Infotech,
On what basis you are fixing up the time for project completion?
Why is it important to thoroughly retest a defect after it has been reported fixed? How will you do that?
what is be bugging ?
How do we measure quality of testing? What are parameter of this?
what is an inconsistent bug? how to resolve this kind of bugs?
WHAT IS PROTOCAL TESTING..EXPLAIN? L2, L3 PROTOCALS TESTING MEANS WHAT?EXPLAIN BRIEFLY
what is the difference between test strategy and test plan?
Can any one share the domain knwoldege of Telecom Jeeva jeevachr@gmail.com
What is Usability testing, pls explain with example.
Automation Testing 
