Software Testing Lifecycle (STLC) Module 4

 SOFTWARE TESTING LIFESYCLE (STLC)

Software testing is a structured process that is performed after or along with software development to ensure the application works correctly and meets user requirements.

The Software Testing Life Cycle (STLC) defines step-by-step testing activities to ensure software quality.




Phases of Software Testing Life Cycle (STLC)

1. Requirement Analysis

This is the first phase of STLC.

What happens here

  • Tester understands requirements

  • Identifies what to test

  • Finds unclear or missing requirements

  • Thinks about what may break

Documents created

  • Requirement Traceability Matrix (RTM)

  • Requirement clarification notes

Example (Online Login System)

  • What happens if password is wrong?

  • Is OTP required?

  • How many login attempts are allowed?


2. Test Planning

Test planning is where decisions are made.

Test Plan is a blueprint of testing activities.
It acts like a contract between testing team and project team.

Test plan answers

  • What type of testing?

  • Who will test?

  • Timeline

  • Tools

  • Risks and backup plan

Important contents of Test Plan

  • Test deliverables (test cases, defect reports, test summary)

  • Test environment (hardware, software, network, tools)

  • Roles & responsibilities

  • Schedule

  • Entry & Exit criteria

  • Risk & contingency plan

  • Approval

Example

  • Manual testing for login

  • Tester: QA team

  • Tool: Excel, Jira

  • Exit criteria: All critical bugs fixed


Test Plan vs Project Plan

Test PlanProject Plan
Limited to testingCovers entire project
QA focusedAll stakeholders involved
Individual approachHolistic approach

Test Plan vs Test Strategy

Test StrategyTest Plan
Why & How to testWhat, When, Who
High-levelDetailed
Long-termProject-specific

3. Test Case Design / Test Case Development

A test case is a structured document with:

  • Steps

  • Action

  • Expected result

Types of test cases

  • Positive test case

  • Negative test case

Example

Test CaseActionExpected Result
TC_01Enter valid login detailsLogin success
TC_02Enter wrong passwordError message

Related terms

  • Test scenario: What to test

  • Test case: How to test

  • Test data: Input values


4. Test Environment Setup

This phase ensures the testing system is ready.

Includes

  • Hardware

  • Software

  • Network

  • Tools

Document created

  • Environment setup checklist

Example

  • Browser: Chrome

  • Database connection active

  • Server running


5. Test Execution

In this phase, testers execute test cases and log defects.

What happens

  • Run test cases

  • Mark result as Pass / Fail

  • Log bugs if test fails

Example

  • TC_01 → Pass

  • TC_02 → Fail → Bug logged

Bug report / Defect report is created


6. Test Cycle Closure

This is the final phase of STLC.

Testing is formally closed here.

Activities

  • Test summary report

  • Lessons learned

  • Test closure report

Example

  • Total test cases: 100

  • Passed: 95

  • Failed: 5

  • Critical bugs fixed

esting Techniques (From Your Notes)

Black Box Testing

Tester does not know internal code.

Techniques

  • Boundary Value Testing
    Example: Password length 8–16 → test 7, 8, 16, 17

  • Equivalence Partitioning
    Example: Valid vs Invalid inputs


White Box Testing

Tester checks internal code logic.

Technique

  • Code coverage testing


Experience Based Testing

Testing based on tester’s domain experience and intuition.


Testing Tools

Common tools used:

  • Jira

  • Excel

  • Bugzilla

Comments

Popular posts from this blog

Software Testing Module 2

Assignment 1

Assignment 3