SDLC

Requirement:

1. Business Analyst collects the requirement from the Customer/Client as per the clients business
needs and documents the requirements in the Business Requirement Specification

Analysis Phase:

1. Define Product Requirement

2. Products to be developed, Key people involved in – Project Manager, Business Analyst, Senior
Members
3. Software Requirment Specification

Design Phase:
 1. HLD – Architecture of the Software Product. Done by Senior Developers and architects
2. LLD – Done by Senior Developers. Describes How each and every component should work

Development Phase:

1. Code Development

Testing Phase:

1. Product Testing

Deployment:

1. Deploy the product into Product Environment

STLC:

Requirement Analysis
During this phase, test team studies the requirements from a testing point of view to identify the
testable requirements.

The QA team may interact with various stakeholders (Client, Business Analyst, Technical Leads, System
Architects etc) to understand the requirements in detail.

Automation feasibility for the given testing project is also done in this stage. Activities

 Identify types of tests to be performed.

 Prepare Requirement Traceability Matrix (RTM).
 Automation feasibility analysis (if required).

Deliverables

 RTM
 Automation feasibility report. (if applicable)

Test Planning

Typically , in this stage, a Senior QA manager will determine effort and cost estimates for the project and
would prepare and finalize the Test Plan. In this phase, Test Strategy is also determined.

Activities

 Detailed Requirements
 Preparation of test plan/strategy document for various types of testing
 Test tool selection
 Test effort estimation
 Resource planning and determining roles and responsibilities.
 Training requirement
 Dependencies
 Risks

Deliverables

 Test plan /strategy document.

 Effort estimation document.

Test Case Development

This phase involves creation, verification and rework of test cases & test scripts. Test data , is
identified/created and is reviewed and then reworked as well. Activities

 Create test cases, automation scripts (if applicable)

 Review and baseline test cases and scripts
 Create test data (If Test Environment is available)
Deliverables

 Test cases/scripts
 Test data

Test Environment Setup

Test environment decides the software and hardware conditions under which a work product is tested.
Test team may not be involved in this activity if the customer/development team provides the test
environment in which case the test team is required to do a readiness check (smoke testing) of the given
environment. Activities

 Perform smoke test on the build

Deliverables

 Environment ready with test data set up

 Smoke Test Results.

Test Execution

During this phase the testers 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

 Document test results, and log defects for failed cases
 Map defects to test cases in RTM
 Retest the Defect fixes
 Track the defects to closure

Deliverables

 Completed RTM with execution status

 Test cases updated with results
 Defect reports

Test Cycle Closure

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. The idea is to remove the process
bottlenecks for future test cycles and share best practices for any similar projects in future.Activities

 Evaluate cycle completion criteria based on Time,Test coverage,Cost,Software,Critical Business

Objectives , Quality
 Prepare test metrics based on the above parameters.
  Document the learning out of the project
 Prepare Test closure report
 Test result analysis to find out the defect distribution by type and severity.

Deliverables

 Test Closure report

 Test metrics

Testing Methodologies

V&V Model (Verification and Validation Model):

Agile Methodology:

Scrum Process:
Scrum Ceremonies:

Scrum: Sugges Three Roles – Scrum Master , Product Owner and The Team (Devlopment and Testing
Team) and scrum ceremonies are Daily Scrum, Sprint Planning, Sprint Review/Demonstration and
Retrospective Meetings.

Spring Planning: The entire team agrees to complete a set of product backlog items within a Sprint
based on the team velocity and it will be defined as sprint backlog. This will be happening before the
sprint get started and mostly the duration wil be one hour

Daily Stand up: It will be happening on a daily basis for 15 mins where status of each story/person wil be
discussed and any road blocks will be addressed.

Sprint Review/Demonstration : A Sprint Review/Demo meeting is held at the end of the Sprint. The
Team demonstrates the user stores to the product owner according to the Definition of Done. The
Product Owner reviews and accepts the delivered Increment.

Sprint Retrospective: The sprint retrospective is a meeting facilitated by the Scrum Master at the end of
the sprint where – What went wrong, What can be improved and What went well will be discussed.

Defect Life Cycle:

Types of Testing:

1. Manual Testing

1. Regression Testing = To Ensure the Existing functionalities of the application is behaving as

expected and no functionalities are broken with the recent builds

2. Functional Testing = Validate the functionality of the application.

3. Smoke Testing = To validate only high priority functionalities of the application

4. Sanity Testing = High level functionalities of Specific Module

5. Adhoc Testing = Quick round of testing will be perfomed for any defect fixes and build
changes

6. Exploratory Testing = Based on the experience, Explore the application and validate the
functionalities without any specific Test Cases.

7. Boundary Value Analysis = Validate the boundary ranges

8. Cross Browser Testing = To check in different browsers.

9. Equivalance Partition Testing = Partition the ranges and check one random value from each
partition. For Eg 1 – 100 (Partition to 1 – 250, 251 – 500, 50 1- 750, 751 - 1000)

10. Integration Testing = Integration testing is the phase in software testing in which individual
software modules are combined and tested as a group.
 11. Alpha Testing = Alpha Testing is a type of software testing performed to identify bugs before
releasing the product to real users or to the public. Alpha Testing is one of the user acceptance testing.

12. Beta Testing is performed by real users of the software application in a real environment.
Beta testing is one of the type of User Acceptance Testing.

13. Retesting = Retesting is testing of a particular bug after it has been fixed.

2. Automation Testing = Performed using automation scripts

3. Performance Testing

- Load Testing

- Stress Testing

- Volume Testing -

4. Security Testing

5. White Box Testing

- Unit Testing = Developed code will be validated with Unit Test Scripts