Answers for "what is test plan"

what is test plan

A Test Plan is a detailed document that describes
the test strategy, objectives, schedule, 
estimation, deliverables, and resources
required to perform testing for a software product

what test plan contains

Test Plan Identifier
References
Introduction
Test Items
Features To Be Tested
Features Not To Be Tested
Approach
Pass/Fail Criteria
Suspension Criteria
Test Deliverables
Testing Tasks
Environmental Needs
Responsibilities
Staffing and Training Needs
Schedule
Risks and Contingencies
Approvals

how to write a test plan

Analyze the product
Design the Test Strategy
Define the Test Objectives
Define Test Criteria
Resource Planning
Plan Test Environment
Schedule & Estimation
Determine Test Deliverables

test plan identifier

Test Plan Identifier is a unique number to identify the test plan.

How to write a Test Plan?

Test Plan is the most important task of Test Management Process
1. OBJECTIVE:
*Test Plan is to define scope of the testing, schedules and 
testing tools.
2. REFERENCE DOCUMENTS:
User Stories and Acceptance Criteria Link for document
3. AREAS TO BE TESTED:
● Map ● Schedule ● End User Authorization
4. AREAS NOT REQUIRING TESTING
5. HIGH LEVEL TEST OVERVIEW 
*INTEGRATION TESTS *SMOKE TESTS
6. ACCEPTANCE TESTS:(UAT) team will be responsible
7. REGRESSION TESTING:
8. BROWSER COVERAGE:
1. IE (Internet Explorer) 2. Chrome 3. Firefox
9. AUTOMATION STRATEGY:
● Use Java for main language
● use Maven/Selenium/Lambda Test for front-end testing.
● use Cucumber Framework ..etc
10. TESTING TIME LINES/SCHEDULES
11. TESTING STRATEGY
● Existing functionalities will be validated
● New functionalities will be validated 
● Fixed defects will be validated.
12. RESOURCES
*Human Resources:
*Software/Hardware Resources (Technical Resources)
13. RISKS & MITIGATION: (Business Team)
14. ENTRY CRITERIA
● Requirement Specification Document (P.O + B.A)
15. EXIT CRITERIA:
● Completion of Planned Test Cases Execution

what is test plan

A Test Plan is a detailed document that describes
the test strategy, objectives, schedule, 
estimation, deliverables, and resources
required to perform testing for a software product

what test plan contains

Test Plan Identifier
References
Introduction
Test Items
Features To Be Tested
Features Not To Be Tested
Approach
Pass/Fail Criteria
Suspension Criteria
Test Deliverables
Testing Tasks
Environmental Needs
Responsibilities
Staffing and Training Needs
Schedule
Risks and Contingencies
Approvals

how to write a test plan

Analyze the product
Design the Test Strategy
Define the Test Objectives
Define Test Criteria
Resource Planning
Plan Test Environment
Schedule & Estimation
Determine Test Deliverables

test plan identifier

Test Plan Identifier is a unique number to identify the test plan.

How to write a Test Plan?

Test Plan is the most important task of Test Management Process
1. OBJECTIVE:
*Test Plan is to define scope of the testing, schedules and 
testing tools.
2. REFERENCE DOCUMENTS:
User Stories and Acceptance Criteria Link for document
3. AREAS TO BE TESTED:
● Map ● Schedule ● End User Authorization
4. AREAS NOT REQUIRING TESTING
5. HIGH LEVEL TEST OVERVIEW 
*INTEGRATION TESTS *SMOKE TESTS
6. ACCEPTANCE TESTS:(UAT) team will be responsible
7. REGRESSION TESTING:
8. BROWSER COVERAGE:
1. IE (Internet Explorer) 2. Chrome 3. Firefox
9. AUTOMATION STRATEGY:
● Use Java for main language
● use Maven/Selenium/Lambda Test for front-end testing.
● use Cucumber Framework ..etc
10. TESTING TIME LINES/SCHEDULES
11. TESTING STRATEGY
● Existing functionalities will be validated
● New functionalities will be validated 
● Fixed defects will be validated.
12. RESOURCES
*Human Resources:
*Software/Hardware Resources (Technical Resources)
13. RISKS & MITIGATION: (Business Team)
14. ENTRY CRITERIA
● Requirement Specification Document (P.O + B.A)
15. EXIT CRITERIA:
● Completion of Planned Test Cases Execution