Scribd
Upload
16 views3 pages

Day 8

The Software Testing Life Cycle (STLC) consists of sequential phases including Requirement Analysis, Test Planning, Test Case Design, Test Environment Setup, Test Execution, and Test Closure, aimed at ensuring software quality. Various testing methods such as Unit Testing, Functional Testing, Integration Testing, Regression Testing, User Acceptance Testing, Black Box Testing, and White Box Testing are employed to validate software functionality and performance. Defect management is a crucial process that involves identifying, tracking, and resolving defects to ensure minimal issues in the software delivery.

Uploaded by

Divya S
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
16 views3 pages

Day 8

The Software Testing Life Cycle (STLC) consists of sequential phases including Requirement Analysis, Test Planning, Test Case Design, Test Environment Setup, Test Execution, and Test Closure, aimed at ensuring software quality. Various testing methods such as Unit Testing, Functional Testing, Integration Testing, Regression Testing, User Acceptance Testing, Black Box Testing, and White Box Testing are employed to validate software functionality and performance. Defect management is a crucial process that involves identifying, tracking, and resolving defects to ensure minimal issues in the software delivery.

Uploaded by

Divya S
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

Software Testing Life Cycle:

The Software Testing Life Cycle (STLC) is a series of phases that guide the testing
process to ensure software quality. Development life cycle is followed by the
testing life cycle. A testing life cycle comprises of several phases and activities
aligned in a sequential manner to initiate, execute and terminate the testing
process.
A software testing process could be initiated as soon as the development process
begins and may be carried out in parallel to the development activities. The
following are the stages of STLC.

1. Requirement Analysis:- This initial phase involves reviewing and


understanding the requirements and specifications of the software. Testers assess
the requirements for testability to identify what needs to be tested and how, i.e.
those requirements which may produce results on feeding with the input data.
2. Test Planning:-
With the information gathered about the requirements in the previous phase, QA team
move a step ahead in the direction of planning the testing process. Basically, a
strategy or strategies is/are defined and described for the testing
process/activities.
3.Test Case Design & Development:-
The requirements has got analysed and accordingly the QA team comes out with a test
plan. Based on test plan and detailed requirements, test cases are designed and
developed for the purpose of verifying and validating each and every requirements
specified in the documentation.
4.Test Environment Setup:-
The software testing process needs an appropriate platform and environment
encompassing the necessary and required hardware and software, to create and
replicate the favourable conditions and intended environmental factors to perform
actual testing activities i.e. execution of the developed test cases on the
software.
5.Test Execution:-
With the test cases, test data and the suitable test environment, QA team is now
ready to actual testing activities. The test execution phase involves the execution
of the developed test cases with the help of test data in the set up test
environment.
6.Test Closure:-
The completion of the test execution phase and delivery of the software product
marks the beginning of the test closure phase. This phase perceives the meeting and
discussion amongst the QA team members with respect to test execution and its
results. Apart from the test results, other testing related parameters are
considered and reviewed such as quality achieved, test coverage, test metrics,
project cost, adherence to deadlines, etc.
...

Manual & Automation testing

Unit Testing

Tests individual components or functions of the software to ensure they work


as intended. It is a test to check the code whether it is properly working or not
as per the
requirement. It is done by the developers (Not testers).

Functional Testing

It is a test to check whether each and every functionality of that


application is
working as per the requirement. It is major test where 80% of the tests are done.
In this test, the Test
Cases are ‘executed’.

Integration Testing

Validates the interactions between different components or systems to ensure


they work together correctly. It is to check whether all the modules are combined
together or not and
working successfully as specified in the requirements.

Regression Testing

When a functionality is added to an application, we need to make sure that


the newly added functionality does not break the application. In order to make it
sure, we perform a
repeated testing which is called Regression Testing. We also do regression testing
after the developers fix the bugs.

User Acceptance Testing

Validates that the software meets user needs and business requirements before
it is deployed.

Black box Testing

It is test where a tester performs testing without looking into the code. Or
A testing method where the application under test is viewed as a black box and the
internal behavior of the program is completely ignored. Testing occurs based upon
the external specifications. Also known as behavioral testing, since only the
external behavior of the program is valuated and analyzed.
Black box testing involves testing the software without any knowledge of its
internal code, structure, or implementation details. Testers focus on evaluating
the functionality of the application based on its specifications and requirements.

White box Testing

White box testing, also known as clear box or structural testing, involves
testing the software with knowledge of its internal code, structure, and logic.
Testers use their understanding of the code to design test cases and ensure that
all code paths are tested.

Test case:

A Test Case is a document that describes step by step process how to test the
application. A Test Case includes Test Case ID, Steps Description, Expected Output,
Actual Output, Pass/Fail, Remarks.

Defect management

Defect management is a critical process in software development and quality


assurance that involves identifying, tracking, managing, and resolving defects (or
bugs) in a software application. The goal of defect management is to ensure that
software is delivered with minimal defects and that any issues are addressed in a
systematic and efficient manner. Investment in defect management tool is crucial
since the tracking of defect from the early stages is quite an easiest way to fix
the defect and also having these recorded in defect management tool will provide a
learning advantage for the future reference and helps in avoiding the same
mistakes.

Defect management process flow:

Defect Detection: Identify and document defects.


Defect Categorization: The defect passes to the desired person who checks it and
categorize it into what type of defect.
Defect Prioritization: Based on the type/severity of the defects, they get
prioritized accordingly.
Defect Assignment: Assign defects to appropriate team members.
Defect Analysis: Assess the impact and root cause.
Defect Resolution: Fix the defect and document the solution.
Defect Verification: Retest and confirm the fix.
Defect Closure: Mark the defect as resolved and close it.
Management Reporting: Analyze and report defect data to the respective
stakeholders.

You might also like