8. Testing Workflow Across Development Lifecycle
← Previous: Preparation Phase | Back to QA Strategy | Next: Defect Management →
This section describes the testing workflow used throughout the development lifecycle at Spline Studio. The workflow defines how QA activities are performed from sprint planning through post-release validation.
Testing Workflow Overview
The testing workflow is iterative and adapts to the development process. At several stages, identified issues may require returning to defect fixing and re-verification before testing can proceed further.
flowchart TB
A["Sprint Test Planning"] --> B["Requirements &<br>Design Analysis"]
B --> C["Test Design"]
C --> D["Feature Testing"]
D --> F["Final Feature<br>Validation"]
F --> G["Integration Testing"]
G --> H["Smoke Testing"] & M["Test Automation Phase"]
H --> I["System Testing"]
I --> J["Regression Testing"]
J --> K["Acceptance Testing"]
K --> L["Post-Release<br>Validation"]
D -. Issue Found .-> BD["Bug Fix<br>Feature Testing"]
G -. Issue Found .-> BG["Bug Fix<br>Integration Testing"]
H -. Issue Found .-> BH["Bug Fix<br>Smoke Testing"]
I -. Issue Found .-> BI["Bug Fix<br>System Testing"]
J -. Issue Found .-> BJ["Bug Fix<br>Regression Testing"]
BD -. Fix .-> D
BG -. Fix .-> G
BH -. Fix .-> H
BI -. Fix .-> I
BJ -. Fix .-> J
n4["DEV"]
n2["Pre-Prod"]
n1["RC"]
n3["PROD"]
style A fill:#ffffff,color:#000000
style B fill:#ffffff,color:#000000
style C fill:#ffffff,color:#000000
style D fill:#C8E6C9,color:#000000
style F fill:#C8E6C9,color:#000000
style G fill:#C8E6C9,color:#000000
style H fill:#FFF9C4,color:#000000
style M fill:#BBDEFB,color:#000000
style I fill:#FFF9C4,color:#000000
style J fill:#FFF9C4,color:#000000
style K fill:#FF6D00,color:#000000
style L fill:#FFCDD2,color:#000000
style BD fill:#E1BEE7,color:#000000
style BG fill:#E1BEE7,color:#000000
style BH fill:#E1BEE7,color:#000000
style BI fill:#E1BEE7,color:#000000
style BJ fill:#E1BEE7,color:#000000
style n4 fill:#C8E6C9,color:#000000
style n2 fill:#FFF9C4,color:#000000
style n1 fill:#FF6D00,color:#000000
style n3 fill:#FFCDD2,color:#000000
linkStyle 6 stroke:#000000,fill:none
linkStyle 11 stroke:#D32F2F,stroke-width:2px,stroke-dasharray:6 4,fill:none
linkStyle 12 stroke:#D32F2F,stroke-width:2px,stroke-dasharray:6 4,fill:none
linkStyle 13 stroke:#D32F2F,stroke-width:2px,stroke-dasharray:6 4,fill:none
linkStyle 14 stroke:#D32F2F,stroke-width:2px,stroke-dasharray:6 4,fill:none
linkStyle 15 stroke:#D32F2F,fill:none
linkStyle 16 stroke:#00C853,stroke-width:2px,fill:none
linkStyle 17 stroke:#00C853,stroke-width:2px,fill:none
linkStyle 18 stroke:#00C853,stroke-width:2px,fill:none
linkStyle 19 stroke:#00C853,stroke-width:2px,fill:none
linkStyle 20 stroke:#00C853Workflow Phases
Sprint & Planning
At the beginning of each sprint, QA reviews the planned scope and prepares the testing approach for the upcoming cycle.
Requirements & Test Preparation
2. Requirements & Design Analysis
QA reviews documentation, wireframes, and designs to identify inconsistencies and prepare for test design.
QA creates structured test cases and scenarios based on analyzed requirements and design specifications.
Feature Validation
QA performs functional validation of implemented features using structured and exploratory testing techniques.
5. Bug Fix Verification & Test Case Updates
QA verifies that reported defects have been resolved and updates test cases as needed.
QA performs final validation to confirm the feature works correctly after all fixes.
Integration testing
QA verifies how the implemented feature interacts with other system components and existing functionality after final feature validation.
Test automation phase
QA automates stable and critical test scenarios to support regression and improve testing efficiency across future releases.
Pre-Production Validation
9. Smoke Testing (Pre-Production)
QA performs smoke testing to verify that the build is stable before full system testing begins.
10. System Testing (Pre-Production Validation)
QA validates new functionality within the complete system environment before release.
QA ensures that new changes do not negatively impact existing system functionality.
QA validates that the system meets business requirements and is ready for release.
Production Validation
After deployment, QA performs limited validation to confirm critical functionality operates correctly in production.
Workflow Characteristics
Iterative Nature
The testing workflow is iterative. When issues are identified during feature testing, system testing, or regression testing, the workflow returns to bug fix verification before proceeding.
Environment Progression
Testing progresses through multiple environments: - DEV – Feature testing, integration testing and bug fix verification - Pre-Production – Smoke testing, system testing, regression testing - RC (Release Candidate) – Acceptance testing - Production – Post-release validation
Continuous Feedback
QA provides continuous feedback to development and product teams throughout the workflow, ensuring quality issues are identified and addressed early.
Flexible Execution
The workflow adapts to project needs. Not all phases may be required for every feature or release, depending on scope and risk assessment.
Workflow Integration
The testing workflow integrates with: - Sprint Planning – QA participates in planning and estimation - Development Process – QA collaborates with developers throughout implementation - Release Management – QA provides quality signals for release decisions - Defect Management – Issues flow through the defect management process - Automation – Automated tests support regression and smoke testing activities
← Previous: Preparation Phase | Back to QA Strategy | Next: Defect Management →