STLC

-

STLC

STLC stands for Software Testing Life Cycle. STLC is a process where all the components and features of an application are tested completely such that they satisfy the requirements and quality as per the standard.  STLC involves strategic testing that needs to be carried out in each phase of development

The saying “prevention is better than cure” perfectly applies to software testing. Instead of spending a lot of time, money, and resources fixing problems after they occur, the Software Testing Life Cycle (STLC) ensures testing happens throughout every phase of development. This continuous testing helps catch issues early, leading to a high-quality product delivered on time and within budget.

By following the STLC, testing is done step-by-step as each part of the software is built. This allows teams to find and fix blockers or bugs early, preventing major problems later. As a result, the final product meets the expectations of stakeholders, clients, and customers without unexpected delays or costs.

6 phases of Software Testing Life Cycle


1. Requirement Analysis

Testers review the requirements to understand what needs to be tested. They identify testable requirements and clarify any doubts with the stakeholders.

2. Test Planning

The testing team creates a test plan, deciding the scope, approach, resources, schedule, and types of testing to be done.

3. Test Case Development

Testers write detailed test cases and prepare test data based on the requirements and test plan.

4. Test Environment Setup

The required hardware and software environment is prepared to execute the test cases.

5. Test Execution

Testers run the test cases on the software. They log any defects or issues found during testing.

6. Test Cycle Closure

After testing is complete, the team reviews the testing process, documents lessons learned, and prepares test summary reports.

Software Testing Life Cycle (STLC) – Phases with Examples

Phase

Description

Example

1. Requirement Analysis

Understand what needs to be tested.

Login feature: Check if username & password fields are testable.

2. Test Planning

Create a test strategy, timeline, and assign roles.

Decide to use 2 testers, run manual tests for login, automate sign-up flow.

3. Test Case Development

Write test cases and prepare test data.

Write steps: "Enter username → Enter password → Click Login → Expect success."

4. Test Environment Setup

Set up the software, hardware, and tools needed for testing.

Install app on test server, configure Chrome browser and database access.

5. Test Execution

Run the test cases and log bugs.

Run login test → System crashes → Log defect in bug tracker.

6. Test Cycle Closure

Wrap up testing, report results, and reflect.

Prepare test summary → Discuss lessons learned → Close open defects.


Comments

Post a Comment

Popular posts from this blog

Non-Functional Testing

-
Non-Functional Testing Non-functional testing  is an important part of software testing that checks how well the system works rather than what it does. It focuses on quality aspects like  performance ,  security ,  usability , and  reliability  to ensure the software is stable, efficient, and ready for users. Types of Non Functional Testing in Software Testing Non-functional testing types encompass a broad spectrum of testing types, each evaluating the software’s performance and usability. 1. Performance Testing Assess how fast and responsive the application is under different conditions. It measures metrics like response time, load time, and throughput to ensure smooth operation under typical usage. 2. Load Testing Simulates expected user traffic or transaction levels to check for performance bottlenecks. This helps identify whether the application can handle the anticipated load before going live. 3. Stress Testing Pushes the system well beyond normal ope...
Read more

Black Box Testing and White Box Testing

-
Black Box Testing and White Box Testing Black box and white box testing are distinct methodologies with opposing objectives. However, they can complement each other to improve testing effectiveness. Black box testing evaluates an application from the user's perspective, while white box testing examines the code and internal design. Black box Testing Black box testing  is a way of testing software without looking at its internal code or design. Testers check if the software works as expected by using the requirements and specifications. They enter data, watch the outputs, and see how the system responds, including how fast and reliable it is. This method can be used at many levels of testing, like unit, integration, system, and acceptance testing, but it’s mostly used in higher-level tests. Testers don’t need coding knowledge—they just focus on whether the software does what it should from the user’s perspective. It’s also called specification-based testing or closed box testing bec...
Read more

Use case vs Test Case

-
Use case vs Test Case What is a Use Case? A  use case  is a common concept in software development that explains how a user interacts with a system to achieve a specific goal. It shows step-by-step what happens during the interaction, including inputs, outputs, and expected behavior. Use cases can be written as text or shown in diagrams, helping teams understand what the system should do from the user's point of view. What is a Test Case? A  test case  is a set of instructions created by testers to check if a specific feature or function of a software application works correctly. It includes the test inputs, conditions, and the expected results. Test cases help find bugs and ensure the software is reliable and meets the requirements. Each test case should be clear, linked to the correct feature, and well-documented. Managing test cases properly is key to successful testing and delivering a high-quality product. Difference between Use Case and Test Case Use case Test ...
Read more