Software Testing Life Cycle K12 Sector

Software Testing Life Cycle The process of testing a software in a well planned and systematic way is known as software testing lifecycle (STLC)

Software Testing Life Cycle Inner Page layout

Requirement Analysis During this phase, Test team studies the requirements from a testing point of view to identify the testable requirements. Team have to interact with various stakeholders (Client, Business Analyst, Technical Leads, System Architects etc) to understand the requirements in detail. Requirements could be either Functional (defining what the software must do) or Non Functional (defining system performance /security availability ). Activities Identify types of tests to be performed.  Gather details about testing priorities and focus. Identify test environment details where testing is supposed to be carried out. 

Test Plan Preparation Test plan: A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, the test environment, the test design techniques and entry and exit criteria to be used, and any risks requiring contingency planning. Typically , in this stage, will determine effort estimates for the project. Activities Preparation of test plan/strategy document Test effort estimation  Resource planning and determining roles and responsibilities. Training requirement

Test Scenario/Test Cases Test Scenario includes the functionality/feature as a WHOLE and Test Cases include the functionality/feature in DETAIL testing. Activities Preparation of test Scenarios Preparation of test Cases Review the test cases (Self, Peer to Peer or TL review)

Test Environment A testing environment is a setup of software and hardware on which the testing team is going to perform the testing of the newly built software product. This setup consists of the physical setup which includes hardware, and logical setup that includes Server Operating system, client operating system, database server, front end running environment, browser (if web application), IIS (version on server side) or any other software components required to run this software product. Activities Setting up the Hardware & Software Setting up the OS and Browser(s) Checking the N/W connections.

Test Execution During this phase, test team will carry out the testing based on the test plans and the test cases prepared. Bugs will be reported back to the development team for correction and retesting will be performed. Activities  Execute tests as per plan Run the automation script for smoke test Document test results, and log defects for failed cases  Retest the defect fixes  Track the defects to closure

Defect Log During this phase, Test team will log the Bugs and reporting the same to development team. Activities  Communicate with dev team about Bugs Document Defects, and log into TFS 

Regression Testing The purpose of regression testing is to confirm that a  recent program or code change has not adversely affected existing features. This testing is done to make sure that new code changes should not have side effects on the existing functionalities. It  ensures that old code still works once  the new code changes are done. Regression Testing is required when there is a, Change in requirements and code is modified according to the requirement New feature is added to the software Defect fixing Performance issue fix 

Analysis Testing team will meet , discuss and analyze testing artifacts to identify strategies that have to be implemented in future, taking lessons from the current test cycle. Activities Qualitative and quantitative reporting of quality of the work product to the customer. Test result analysis Document the learning out of the project

Reports During this phase, Lead will prepare various reports for project. Activities Prepare Test Results Prepare QA report Prepare Release Note Prepare Yslow report

Thank you Giridhar.k