STLC

STLC
Software Testing Life Cycle has the below phases in execution of Testing a project
Analysis & Planning
During this phase Analyze the project testing is manual / Automation testing, Identify the budget, Resource required, Types of Testing Required. Also discuss with Business Analyst, Project manager, Business users and understand the Development Schedule, Project Build Release dates, Project Release dates. Forming the Testing Team.
In this phase Test Lead / Manager has to decide what are in scope for testing, Estimations, Budge, Schedules, Type of Testing to be conducted, Identify the deliverables, Approach.
During this phase preparation of high level test plan- is designed to prescribe the scope, approach, resources, and schedule of all testing activities. The plan must identify the items to be tested, Items not to be tested, the types of testing to be performed, the team responsible for testing, the resources and schedule required to complete testing, and the risks associated with the plan.). All the above details are included in the STP.

Test Design
After Test Plan is prepared / During the Plan KT sessions are also conducted to the Testing Team members to understand the Project Requirements / Functionalities. After understanding the Requirements Test Cases were developed for Functional testing / System Testing. The Test Case should have the Details like TestCaseID, Priority, Test Name, Steps, Description, Expected Results, Actual Results and Status
Test Cases are designed for
Sanity Test Cases
Functional Test Cases
Regression Test Cases
Negative Test Cases
It the project is Automation Test Scripts are developed for the existing Test Cases /Functionalities
Test Execution
The application is validated for the Test cases and check the application is working as per Requirements. To execute the application Test Setup is prepared with the required Environment and the application is tested with Different Test Data.
Reporting & Tracking
Report any Defects to the Development team if any functionality is not working as per the Requirements.
The defect Report should have details
Defect ID, Summary, Detected By, Date, Assigned To, Severity, Priority, Status, Module, Build Ver, Environment, Reproducible, Expected, Actual, Comments
Test Closure
After Testing is completed plan for Test Closure based on if no new defects are found, No risk in the project, all the functionalities are tested and all the defects are closed
General Testing Process in the Company
Whenever we get a new project for Testing we have a initial Project meetings are conducted to get the familiarity of the project and also to understand the details like about the project, scope, is it manual testing / Automation is required? Who are the Development Team, Who is Testing Team, how many resource are required and available, who project manager, about Client, The Technology of the project is like is the project is developed in Java / .Net…etc
Initially for the Team members / Test Lead KT sessions are conducted by the Sr. Resource of the project so that the team can understand about the Project, The Testing Team also can go through the SRS/ FRS…etc or if already developed applications go through the application and understand the project functionality

Based on the Project Requirements Test Plan is prepared as specified in the STLC.
Once the plan is prepared, the Scenarios are derived from the functionalities
For the Scenarios Test Cases are prepared
After the Test Cases are prepared Reviews are conducted to ensure the Test Cases are correct
During this phase as per the planned schedule when the build is released by the Developers Testing is conducted in the Test Environment to ensure the application is working if the application is not working Defects are posted to the developers

Responsibility of a QA Tester
Understand the Project Requirements
Review of the Requirements / Test Requirement Specification (TRS)
Prepare the Scenarios
Design the Test Cases (specified in the above STLC Section)
Validate the application to ensure the application is working as per the req.
Report the Defects to the Development Team and Track the defects.
Ensure the Product / Project satisfies the Standards
Communication with the Business users, Developers