1. Software Testing Life Cycle (STLC)
Various stages involved in this
1. Test Planning
2. Test Development
3. Test Execution
4. Test Result Analysis
5. Bug Tracking / Defect Tracking
6. Defect Reporting
---
1. Test Planning
· It is defined as a strategic doc which explains the overall procedure of how to test total application in a most effective and efficient way.
· It contains test objective, Test scope,
2. Test Development
3. Test Execution
4. Test Result Analysis
5. Bug Tracking / Defect Tracking
6. Defect Reporting
---
1. Test Planning
· It is defined as a strategic doc which explains the overall procedure of how to test total application in a most effective and efficient way.
· It contains test objective, Test scope,
. What are the areas to be tested,
. What are the areas not to be tested, the areas to be automated tools used etc.
· It is Prepared by QL(Quality lead) or S/W QM(Quality Manager)
· The input document for the test plan is project plan. PM prepare project plan.
2. Test Development
· Test Case preparation
· Test Procedure preparation: It is nothing but description of the Test Case Preparation.
3. Test Execution
· Implementation of the Test Case on an application, that means execute the prepared test cases on the application.
· Actual behavior of the application is observed.
4. Test Result Analysis
· After execute the test cases analyze the test result.
· What is supposed to be? What is actually?
· Test Result Analysis will be expressed interns of pass or fail.
· Actual Value: actual behavior of an application
· Expected Value: expected behavior of an application.
5. Bug Tracking / Defect Tracking
.If deviation from the requirements is done then we get a defect.
.Bug tracking is identify the defects
After find the defects list them in separate document is called defect profile.
1. Defect Reporting: TE => Bugs => Developer
Report Document and Defect Profile are not same.
In this phase in which Testing Teams send the defect profile to the Development team for bug fixation. For bug fixation also they may prepare the reporting document which describes the status of the module precisely. Which can be sent to high level management and also to the customer if he requires to them know about status.
TE => Rep. Doc => Status of Module (Customer if required)
TE => Rep. Doc => High Level management (HOO+TM)
-----------------------------------------------------------------------------------------
Related STLC Links:
2. When to start testing?
3. What is Test Case?
4. Explain how to designing Test Case with Real Time Examples:
1. How do I start creating test case / test plan as a new tester?
5. What is Test Plan, Explain in-detail?
6. What is Use Case, Explain?
7. What is Testing Process?
8. When should testing be stopped?
9. General Test Cases
***
. What are the areas not to be tested, the areas to be automated tools used etc.
· It is Prepared by QL(Quality lead) or S/W QM(Quality Manager)
· The input document for the test plan is project plan. PM prepare project plan.
2. Test Development
· Test Case preparation
· Test Procedure preparation: It is nothing but description of the Test Case Preparation.
3. Test Execution
· Implementation of the Test Case on an application, that means execute the prepared test cases on the application.
· Actual behavior of the application is observed.
4. Test Result Analysis
· After execute the test cases analyze the test result.
· What is supposed to be? What is actually?
· Test Result Analysis will be expressed interns of pass or fail.
· Actual Value: actual behavior of an application
· Expected Value: expected behavior of an application.
5. Bug Tracking / Defect Tracking
.If deviation from the requirements is done then we get a defect.
.Bug tracking is identify the defects
After find the defects list them in separate document is called defect profile.
Severity
|
Priority
|
It is to say How Sever the defect
is.
|
How early the defect should be
fixed.
|
High
Medium
Low
Suggestion
|
High
Medium
Low
|
1. Defect Reporting: TE => Bugs => Developer
Report Document and Defect Profile are not same.
In this phase in which Testing Teams send the defect profile to the Development team for bug fixation. For bug fixation also they may prepare the reporting document which describes the status of the module precisely. Which can be sent to high level management and also to the customer if he requires to them know about status.
TE => Rep. Doc => Status of Module (Customer if required)
TE => Rep. Doc => High Level management (HOO+TM)
-----------------------------------------------------------------------------------------
Related STLC Links:
2. When to start testing?
3. What is Test Case?
4. Explain how to designing Test Case with Real Time Examples:
1. How do I start creating test case / test plan as a new tester?
5. What is Test Plan, Explain in-detail?
6. What is Use Case, Explain?
7. What is Testing Process?
8. When should testing be stopped?
9. General Test Cases
***
No comments:
Post a Comment