Software Testing Life Cycle
What is Software Testing Life Cycle STLC?
Software testing Life Cycle is a sequence of different activities performed During The testing Process by the testing team of ensure the quality of software. It is the process of entire start to in the testing. Software testing life cycle (STLC) It is type of SDLC.
Software Development Life Cycle(SDLC)
What are the prices of STLC?
- Test initiation testing.
- Test planning Creation.
- Test case preparation.
- Sanity testing.
- Re-testing and regression testing.
- Environmental setup.
- Test case execution.
- Test summary report.
- Test closure report.
1)Test initiation testing: –
It is the first of the software testing life cycle (STLC). for this stage team lead is responsible. Test initiation Testing is nothing but pre-required things. This is known as spring zero. In test initiation, PM Will prepare TRM document, TRM completed, then send to test lead.
Test initiation testing Testing is mainly focus on 3 factors.
- Scope of project
- Requirement of project.
- Risk involved in the project.
Requirement of project
Here, Scrum Master and Team lead will decide the which type of Domain we will use in your upcoming project Like telecom domain/banking domain/Eco mere in insurance domain.
Scope of project: –
Scope of project is nothing, but which type of testing we are going to perform in upcoming project like, auto Motion, API, manual, Database, Security, performance.
Also, we need to check which requirements are present in particular type. Maintain test cases, news upload, test cases on Excel sheet.
Risk involved in the project.
- Which type of risk involved in the SDLC?
in the risk informant Different type of risk occur like,
- Lack of resources
- Lack of software
- Lack of knowledge
- Lack of requirement
- Lack test data
- lack of communication
- Lack of budget
- Lack of delay in delivery
Lack of Resource: –
Resource means People/employee if in project less number of employee present but work is more as compared to employ that time each person Would have get extra Work do.
Lack of software: –
Lack of software means at the time of testing we need multiple tools or S/W that are must but some time we don’t have provide it. It is one of the factors.
Lack of knowledge: –
In your project new person add involved that person should be not aware about domain knowledge that time he / she need to knowledge transfer means KT is required.
Lack of Requirement: –
Before the testing Tester need to all requirement in proper form client. that requirement is not getting in proper way. that time we can’t check the S/W or application.
Lack of test data: –
Team lead gives the test data. We don’t have taste that on that time Don’t perform testing but at that time we have knowledge about domain then he capable to do ad- hoc testing,
because we don’t have test data, but we have knowledge about domain, that time we do Ad-hoc testing.
Lack of communication: –
Lack of communication between testing team lead? development team.
what is test plan?
Test plan: –
test plan is prepared by test lead. test plan will contain, what do test to test, when to test, how to test and KT.
In the test plan mainly focus on 3 factors.
- Resource allocation
- Job allocation
1)Resource allocation: –
Resource is nothing but the people are involved in the project. after resource are allocated then selected the test.
in the resource allocation team is going to finalized
2) Job allocation: –
In the job allocation, allocate the job to Every member This process done from Scrum Master. -In job allocation We will be selected the scenario related to your project base on that get allocate the job.
– job means it is nothing, but which test will get use or selected.
3) Estimation: –
Estimation is focus on three factors i.e., effort, knowledge, complexity.
Estimation is nothing but a start date and end date of the sprint.
In the test plan mainly focus on the how to test? what the to test? Who will be test? once test plane is done will focus on next phase.
Test case preparation: –
In the test case Preparation, we focus on the test case Scenario and test case design.
On the basis of user story tester will Identify the test scenario and also on the basis of the scenario Tester prepare the test cases.
Sanity testing: –
When the development team send the build tool testing team. then the testing team do the sanity testing
and also, it is Called as zero level testing and also tester acceptance testing and build verification testing. In the sanity testing tests check the basic core functionality.
Basically, sanity testing is done after receiving built. After that we moved on the next print.
Resting is nothing but re-execution on some build or application with multiple test data is successfully removed or not.
It is also planned testing. Retesting include defect and they will do necessary changes and give back defect to us again retesting to ensure that defect is removed or not.
Regression testing: –
New functionality added that time we check that functionality impact on another module.
If CR (change request) raised
Then we focus on new functionality and also existing functionality should not disturb due to newly added functionality after that moved to the report that is test summary report.
Test summary report: –
In the test Summary report, we have to give how many test cases are there, how many test cases are there executed, how many test cases are failed, how many defect found as we will as, how many defects Log and how many test cases prepared?
– this report makes from testing team lead. responsible for report.
After the test to summary report move to test Clousery report.
Test Clouser Report: –
It makes by teams’ leader it contains report summary in brief as well as graphical representation of Pei chart.
It is final report after that we can provide to UAT.