Software testing life Cycle
There are 6 phases
1. Test planning
2. Test development
3. Test execution
4. Result analysis
5. Bug tracking
6. Reporting
1. Test planning:
Plan: plan is a strategic document which contains some information that describes how to perform a task in an effective efficient and optimized way.
Optimization: It is a process on utilizing the available resources to their level best and get in the maximum possible output.
Test plan: It is a strategic document which contains some information that describes how to perform testing on an application in an effective, efficient and optimized way.
Test lead will prepare the test plan.
Introduction:
Objective: the purpose of the document will be clearly described here in this section.
Reference document: the list of all the documents that are referred by the test level will be listed out here in this section.
Ex: system requirement specification project plan, SRS, Kick of meeting
Feature to be tested: the list of the entire feature that are within the scope and need to be tested will be mentioned here in this section.
Feature not to be tested: the list of the entire feature that is not planned for testing will be mention here in this section.
Ex:
Test Strategy: test strategy is an organization level tern which is common for the entire project in the application.
Test plan is a project level term which is specific for particular project in the organization.
Levels of testing: the list of all the levels of testing that are maintained in that company will be listed out in this section.
Types of testing: the list of all the types of testing that are perform in that company will be listed out here in this section.
Test design techniques: the list of all the techniques used during developing the test cases in that company will be mentioned here in this company.
Boundary value + Equivalence class partition
Test Metrics: the list of all the metrics that are maintained in that company will be listed out clear in this section. (Noted in strategy document)
Terminology: the list of all the terms used in that company alone with meanings will be mention here in this section.
Automation plan: (regression testing presented automation) the list of all the areas that are plan for automation in that company will be listed out here in this section.
List of automated tool: the list of all the automated tools that are used in that company will be mentioned here in this section.
Base criteria:
Accept criteria: when to stop the testing on that application will be clearly mention in this section.
Suspension criteria: when to suspend the testing on suspend the build will be clearly mention here in this section.
Test deliverable: the list of all the documents that are to be prepared and delivery during the process will be mentioned here in this section.
Test environment: the clear details of the environment that is about to be used for testing that application will be mentioned here in this section.
Resource planning: who has to do what will be planned mentioned here in this section.
Scheduling: the starting date and ending date of each and every task will be plan and mentioned here in this section.
Staff & training: how much staff need to be recruited and what kind of training need to be provide will be mentioned here in this section.
Risk and contingency: the list of all the potential risk that may occur during the process and corresponding solution plan will be mentioned here in this section.
Ex: i. Employee may leave an organization middle of the project
ii. unable to deliver the project within the deadlines
iii. Customer may impose the dead lines
iv. unable to test all the features within the given time
Contingency:
i. employee need to be maintain on bench
ii. what not be tested should be plan in case of imposed dead line
iii. Proper plan ensure
iv. Priority base execution
There are 6 phases
1. Test planning
2. Test development
3. Test execution
4. Result analysis
5. Bug tracking
6. Reporting
1. Test planning:
Plan: plan is a strategic document which contains some information that describes how to perform a task in an effective efficient and optimized way.
Optimization: It is a process on utilizing the available resources to their level best and get in the maximum possible output.
Test plan: It is a strategic document which contains some information that describes how to perform testing on an application in an effective, efficient and optimized way.
Test lead will prepare the test plan.
Introduction:
Objective: the purpose of the document will be clearly described here in this section.
Reference document: the list of all the documents that are referred by the test level will be listed out here in this section.
Ex: system requirement specification project plan, SRS, Kick of meeting
Feature to be tested: the list of the entire feature that are within the scope and need to be tested will be mentioned here in this section.
Feature not to be tested: the list of the entire feature that is not planned for testing will be mention here in this section.
Ex:
1. Out of scope features
2. Low risk features
3. Features that are plan to be in corporate feature
4. Feature that are skipped based on the time construction
Test Strategy: test strategy is an organization level tern which is common for the entire project in the application.
Test plan is a project level term which is specific for particular project in the organization.
Levels of testing: the list of all the levels of testing that are maintained in that company will be listed out in this section.
Types of testing: the list of all the types of testing that are perform in that company will be listed out here in this section.
Test design techniques: the list of all the techniques used during developing the test cases in that company will be mentioned here in this company.
Boundary value + Equivalence class partition
Test Metrics: the list of all the metrics that are maintained in that company will be listed out clear in this section. (Noted in strategy document)
Terminology: the list of all the terms used in that company alone with meanings will be mention here in this section.
Automation plan: (regression testing presented automation) the list of all the areas that are plan for automation in that company will be listed out here in this section.
List of automated tool: the list of all the automated tools that are used in that company will be mentioned here in this section.
Base criteria:
Accept criteria: when to stop the testing on that application will be clearly mention in this section.
Suspension criteria: when to suspend the testing on suspend the build will be clearly mention here in this section.
Test deliverable: the list of all the documents that are to be prepared and delivery during the process will be mentioned here in this section.
Test environment: the clear details of the environment that is about to be used for testing that application will be mentioned here in this section.
Resource planning: who has to do what will be planned mentioned here in this section.
Scheduling: the starting date and ending date of each and every task will be plan and mentioned here in this section.
Staff & training: how much staff need to be recruited and what kind of training need to be provide will be mentioned here in this section.
Risk and contingency: the list of all the potential risk that may occur during the process and corresponding solution plan will be mentioned here in this section.
Ex: i. Employee may leave an organization middle of the project
ii. unable to deliver the project within the deadlines
iii. Customer may impose the dead lines
iv. unable to test all the features within the given time
Contingency:
i. employee need to be maintain on bench
ii. what not be tested should be plan in case of imposed dead line
iii. Proper plan ensure
iv. Priority base execution
Assumption: the list of all the assumption that needs to be assumption by a test engineer will be listed out here in this section.
Approval information: who has approved this document and when it is approved will be mention here this status.
