Tech Notes Documentation
Insights, tutorials, and deep-dives into QA automation and software engineering.
Building E2E Test Automation Architecture from Scratch with Playwright & POM
Last updated: 14 Agustus 2026Understanding In-Depth SDLC & STLC Synchronization in Quality Engineering
Last updated: 12 Agustus 2026End-to-End QA Testing Process: From Risk Analysis and Test Planning to Execution
Last updated: 10 Agustus 2026Why PRD is Crucial: Escaping the Infinite Loop of Back-and-Forth Development
Last updated: 08 Agustus 2026Integrating Playwright into CI/CD Pipelines with GitHub Actions & Docker
Last updated: 05 Agustus 2026Leveraging Claude Code & MCP to Accelerate QA Workflows
Last updated: 03 Agustus 2026Understanding In-Depth SDLC & STLC Synchronization in Quality Engineering
In modern software engineering, product quality does not happen by accident. Quality is the result of close collaboration between SDLC (Software Development Life Cycle) and STLC (Software Testing Life Cycle) running in parallel from day one.
📌 Methodology Context: Waterfall vs. Agile
Before diving into testing mechanics, it is essential to understand the foundational differences between the two primary software development approaches:
- Waterfall (Traditional): A linear, sequential approach where each stage (Requirement → Design → Coding → Testing → Deployment) must complete before the next begins. Testing (STLC) is isolated at the very end.
- Agile (Modern): An iterative, flexible approach. Development is broken down into small cycles called Sprints (typically 2 weeks), where planning, coding, and testing happen continuously within every cycle.
1. SDLC & STLC Parallel Integration Flow Diagram (Agile Model)
Visualization of how testing phases (STLC) tie directly into each software development phase in Agile:
📊 SDLC & STLC Synchronization Flow
2. STLC Phase Anatomy: Entry Criteria, Exit Criteria, & Deliverables
As a mature Quality Engineering standard, STLC phases have strict boundaries defining when a phase can begin (Entry Criteria) and when it is considered complete (Exit Criteria).
| STLC Phase | Entry Criteria | Exit Criteria | Deliverables |
|---|---|---|---|
| 1. Requirement Analysis | PRD / SRS / User Story documents are available. | Documents fully understood, testable requirements identified. | RTM (Requirement Traceability Matrix), Automation Feasibility Report. |
| 2. Test Planning | Finalized RTM and Requirements. | Effort estimation and schedule signed off. | Test Plan / Test Strategy Document. |
| 3. Test Case Development | Approved Test Plan. | Test cases reviewed and test data prepared. | Test Cases, Test Scripts (Automated), Test Data. |
| 4. Environment Setup | Test Plan & System Architecture available. | Environment successfully passes the Smoke Test. | Test Environment Ready, Smoke Test Results. |
| 5. Test Execution | Ready environment, finalized test cases & test data. | All tests executed, defects triaged and logged. | Test Execution Report, Bug/Defect Report. |
| 6. Test Closure | Execution complete, no critical defects remain open. | Release summary report signed off. | Test Summary Report, QA Sign-off, Test Metrics. |
3. Early Synchronization (Shift-Left Testing)
A major pitfall in software engineering is involving QA only after coding is complete. In a mature workflow, STLC starts during the SDLC Requirement Analysis phase. QA engineers evaluate PRD documents to detect ambiguity or logic flaws before developers write the first line of code (focusing on Defect Prevention over Defect Detection).
4. STLC Comparison: Waterfall vs. Agile Approach
STLC execution varies significantly depending on the underlying software development methodology. Here is a direct comparison between traditional Waterfall and modern Agile testing execution:
| Parameter | Waterfall STLC (Sequential) | Agile STLC (Iterative) |
|---|---|---|
| QA Involvement Start | Starts late, only after the SDLC coding/implementation phase is completely finished. | Starts on Day One (*Shift-Left*), actively participating in backlog grooming and requirement analysis. |
| Execution Cycle | Testing is performed once in a large, comprehensive phase near the end of the project (*End-of-Cycle*). | Testing is executed continuously and iteratively within every short *Sprint* (typically 2 weeks). |
| Test Automation | Mainly focuses on manual end-to-end testing at the very end; automation scripts are built late. | Automation (e.g., Playwright/API tests) is built in parallel and integrated directly into the CI/CD pipeline. |
| Defect Management | Bugs are discovered late, making fixes significantly more costly and risky to release schedules. | Bugs are caught and resolved rapidly within the same *Sprint* (*Immediate Feedback Loop*). |
5. Direct STLC to SDLC Mapping in Agile Practices
In Agile methodologies, the SDLC and STLC cycles move extremely fast (typically in 2-week Sprints). The correlation looks like this:
- Test Planning: Formulated during the System Design phase, defining sprint scope, resource allocation, and risk mitigation.
- Test Design: Built while developers are coding, ensuring test cases and Playwright automation frameworks are pre-constructed based on API Contracts/Mocks.
- Test Execution: Active immediately when features hit Staging, tracking defects in JIRA, and executing immediate re-tests within the same sprint.
Conclusion
Synchronizing SDLC and STLC seamlessly, fortified by strict adherence to Entry/Exit Criteria, empowers engineering teams to reduce bug remediation costs by up to 70%, accelerate time-to-market, and deliver high-stability, enterprise-grade products.