STLC-ppt-1.pptx
•Download as PPTX, PDF•
0 likes•28 views
The document discusses the Software Testing Life Cycle (STLC) which consists of 6 phases to ensure software quality goals are met. The 6 phases are: 1) Requirement Analysis where QA interacts with stakeholders to understand requirements, 2) Test Planning where a test plan is created outlining testing activities, efforts, and costs, 3) Test Case Development where test cases and data are created and reviewed, 4) Test Environment Setup where testing conditions are decided, 5) Test Execution where testing is carried out based on test plans and cases, and 6) Test Closure Activities which are done after product delivery and include ensuring test completion and archiving work products.
STLC-ppt-1.pptx
- 2. STLC with QA Software Testing Life Cycle is a sequence of activities conducted during testing process to ensure software quality goals are met. There are 6 major phases in STLC model: PROCESSOF STLCMODEL Requirement Analysis TestPlanning TestCase Development Environment Setup TestExecution TestClosure
- 3. Requirement Analysis ï‚´QA interacts with various stakeholders like Client, Business Analyst, System Analyst, Technical Lead/ Development Manager to understand the requirements in detail to develop the project. ï‚´During this phase the QA takes an important decisions like what are the testing types & techniques to be performed, feasibility for automation testing implementation, etc.
- 4. Test Planning ï‚´It is a document which contains the plan related to all testing activities which needs to be done to deliver a quality product. ï‚´Senior QA Manager determines test plan strategy along with efforts and cost estimates for the project. ï‚´The focus of the is to describe: Testduration Resources Whatto test Whatcannotbe tested Toolsusedfor testing Risksand contingencies planning
- 5. Test Case Development ï‚´Testing team write down all test cases. ï‚´Prepare test data. ï‚´Test cases are reviewed by peer members or QA lead. ï‚´Requirement Traceability Matrix is prepared. The RTM is an industry accepted format for tracking requirements where each test cases is mapped with the requirements using tis RTM. We can track backward and forward traceability. ï‚´OOB thinking.
- 6. Test Environment Setup ï‚´Decides the software and hardware conditions under which a work product is tested. ï‚´It can be done in parallel with test case development phase. ï‚´Generic thing may not repeat for every story. ï‚´Needs to be discussed in sprint grooming. ï‚´We can have multiple QA server.
- 7. Test Execution ï‚´The testers will carry out the testing based on the test plans and the test cases prepared. Bugs are reported to the development team. The development team resolves the bugs and the system is retested to ensure that it is bug free and ready to go live.
- 8. Test Closure Activities ï‚´Test closure activities are done mostly after the product is delivered ï‚´Test closure activities mainly comprise of four types: ï‚´Ensure Test Completion ï‚´Handover Test Artifacts ï‚´Project Retrospectives ï‚´Archive Test Work Products
- 9. THANK YOU