1. Introduction
2. Objective
3. Scope
4. Testing Strategy
A. functional,
B. Regression
C. Gui Testing
D. Automation
5. Identify Required Resource
A. Hardware,
B. Software,
C. Database,
D. Tester,
E. Training and
F. Tools
6. Identify features and functions to test
7. Identify risk and Dependency
A. Resource availability
B. Tester understanding
C. Environment setup
D. Down time
E. Release no giving on mentioned time to QA.
F. High severity defect should resolved on priority
G. Enhancememnt in between
H. Server should be availalbe if is the part of testing
I. Daily/weekly status meeting with client.
J. Complexity of project
8. Estimation
What are the main attributes in Test Plan
Introduction, Scope, Test Strategy, Schedule, Scope and Environment
Have you prepared Test Plan : Yes
What are the Pre Requisite to prepare the Test plan
Project plan, TAD, FSD and complexity Matrix.
How you estimate the Test cases preparation plan
As per the scenario and it's complexity defined in Complexity Matrix
How you estimate the Test Cases Execution plan (scope)
As per the scenario criticalness and it's complexity defined in Complexity Matrix
If you have short time and you have to execute 1000 test cases how can you manage the work
I will prioritize the criticalness and then go for the remaining test cases if there is time.
If you don't know the functionality then how can you estimate the test preparation plan
As i will used my previous experience.
If you don't know the functionality then how can you estimate the test execution plan
As i will used my previous experience
To whom you will contact if there is 10 high severity bugs and your release date is tomorrow.
First i will prioritize the defect criticlness and impact of these defects, and will discussed with TM theses are the impact and will ask for delay.
If today is Project delevery and you got the high severity bug then how you will manage.
Here i will find out the impact of this defect and informed to TM first. We will take call with client these are the impact of this defect and we will release it and we will work on it and fix it within same day and we will deploy new code
When do we prepare a Test Plan?
Always prepared a Test Plan for every new version or release of the product
What is the purpose of a Test plan?
1.preparing it helps us to think through the efforts needed to validate the acceptability of a software product.
2.We create a test plan because it can and will help people outside the test group to understand the why and how of product validation.
3.in regulated environments, we have to have a written test plan.
4.the general testing process includes the creation of a test plan.
5.we want a document that describes the objectives, scope, approach and focus of the software testing effort.
6.it includes test cases, conditions, the test environment, a list of related tasks, pass/fail criteria, and risk assessment.
7. one of the outputs for creating a test strategy is an approved and signed off test plan document.
8.the software testing methodology a three step process, and one of the steps is the creation of a test plan.
9.we want an opportunity to review the test plan with the project team.
10.test plans should be documented, so that they are repeatable.
