Introduction
In real-time projects, manual testing follows a structured workflow to ensure high product quality. Testers are involved from requirement analysis until product release.
This guide explains a practical end-to-end manual testing process used in real IT projects.
Project Overview (Example)
Project: Online Banking Application
- Modules: Login, Account Summary, Fund Transfer, Bill Payment
- Team: Developers, Testers, Business Analyst, Project Manager
- Methodology: Agile Scrum
Complete Manual Testing Workflow
- Requirement Analysis: Review SRS / user stories.
- Test Planning: Define scope, strategy, resources.
- Test Case Design: Write test scenarios and cases.
- Environment Setup: Prepare test environment.
- Test Execution: Execute functional test cases.
- Defect Reporting: Log bugs in tracking tool.
- Re-testing: Verify fixed defects.
- Regression Testing: Ensure no new defects introduced.
- Test Closure: Prepare test summary report.
Testing Documents Used
- Test Plan Document
- Test Case Document
- RTM (Requirement Traceability Matrix)
- Defect Report
- Test Summary Report
Defect Lifecycle in Real Project
- New
- Assigned
- Open
- Fixed
- Retest
- Closed
- Reopen (if needed)
Release Validation
- Final regression testing
- Smoke testing on production
- Sign-off from QA team
- Stakeholder approval
After release validation, the feature is considered production-ready.
Interview Questions
Explain real-time manual testing workflow.
It includes requirement analysis, test planning, test case design, execution, defect reporting, regression testing and release validation.
What documents are prepared in manual testing?
Test Plan, Test Cases, RTM, Defect Report and Test Summary Report.
What is RTM?
Requirement Traceability Matrix ensures all requirements are covered by test cases.
Frequently Asked Questions
When does testing start in a real project?
Testing starts from requirement analysis stage.
Is regression testing mandatory before release?
Yes, it ensures new changes do not break existing functionality.