STLC (Software Testing Life Cycle), is the software testing process which is systematic & well planned. Let’s Quickly have a look on various stage involved in Software Testing Life Cycle (STLC)
STLC Process contains below phases, those are,
1. Requirement Analysis
2. Test Planning
3. Test Design (Test Scenario & Test case Development)
4. Environment Setup
5. Test Execution (Test Execution, Test Results, Defect Reporting, Defect tracking till closure)
6. Test Closure
We will see in details in below Power point.
This is the first step of Software testing life cycle. In this step Quality Assurance (QA) team understands the requirement in terms of what we will testing & figure out the testable requirements.
From very first step QA involved in the where STLC which helps to prevent the introducing defects into Software under test.
Test Plan describes about testing activities to performs on particular Software brief about Workflow of Testing.
Test Plan Contains – Overview of the Test Plan, Scope of the Test Plan, Related Documents, Customers details, Testing Strategy, Testing Scope, Risks, Deliverables, Test Scenarios and Test Cases, Testing Team Roles and Responsibilities, Resource Plan, Testing Schedules, Test Environment, Defect Reporting
Test Design phase consist of Test Scenario & Test case writing.
Test scenarios are to identify what are the possible functionalities to be tested in software or any applications.
Test Scenarios will prepare once the design documents are finalized.
A test case describes what has to test in the software or application in order to verify all client requirements are working properly or not.
Test Execution & Defect Reporting –
In this phase Testers executing the test cases on given build where build note contains.
- Requirements Covered.
- Build ftp path with credentials
- Server details
- DB Queries to add in QA environment.
Once above details are received from development team then we will start executing the test cases. According to test cases execution status (pass/fail) we will update the same in Test Cases document and reports the defects in Test, Management Tools such as HP QC, ALM, Jira, Bugzilla etc.
As per finding the defects in Test results phase, testers have to log a defect in defect management tools.
For example, HP QC/ALM tool.
Each defect should be send to particular developers with proper details and attachments. Try to check the defect in another tester system also.
Once the defects are reported in Test management tools then developer will fix the defect and change the status as fixed.
You will receive email from development team that defect has been fixed, please verify once with new build.
Testers will retest the same reported defect in given new build and mark the status as Close in case defect is fixed and in case still exist then the status will change as Re open.
In this phase testers, will track the defect with status in reports parts, version controls with different versions.
You need to track reported, fixed, closed and re open defects in test management tools.
Once all reported defects are retested and closed then testers will prepare defect closure note with following details
- Open Defects
- Fixed defects
- Re open defects
- Rejected Defects
- Closed defects
- Total Defects
Test Closure Report:
Once the Testing completed with regression testing then Tester has to prepare Test Summary Report, it will contain below details.
- Application details.
- Resource Details.
- Functionality Tested.
- Functionality not tested.
- Defect Found with Number of Test Cycles, Regression Testing.
- What are the Open Defects still not fixed?
- Pre-conditions before roll out in production.