A comprehensive end-to-end manual testing project for an OpenCart-based e-commerce web application, demonstrating complete Software Testing Life Cycle (STLC) implementation with a focus on quality assurance, defect tracking, and requirement traceability.
- Project Overview
- Key Achievements
- Tools & Technologies
- Testing Scope
- Project Structure
- Testing Deliverables
- Key Contributions
- Getting Started
- Test Execution Summary
- Author
This project showcases professional manual testing capabilities applied to a live OpenCart e-commerce platform, ensuring quality and reliability across critical user workflows. The project covers complete STLC phases from requirement analysis to defect closure, with emphasis on functional testing, database validation, and regression testing.
- Platform: OpenCart E-Commerce Web Application
- Environment: Live Production Environment
- Testing Type: Black Box Testing (Functional, UI/UX, Database)
- Methodology: SDLC/STLC (Agile Framework)
β
25+ Test Cases Designed & Executed covering positive, negative, and boundary scenarios
β
100% Requirements Coverage through comprehensive RTM (Requirement Traceability Matrix)
β
8+ Functional Defects Identified with detailed reproduction steps and severity classification
β
Zero Critical Bugs in Production post-regression testing
β
Complete Defect Life Cycle Management ensuring timely resolution of all issues
β
SQL-Based Data Validation for backend data integrity verification
β
Version Controlled Test Artifacts using Git/GitHub for centralized repository management
| Category | Tools/Technologies |
|---|---|
| Testing Type | Manual Testing |
| Test Design | Test Case Design, Boundary Value Analysis, Equivalence Partitioning |
| Defect Tracking | Defect Life Cycle Management, Bug Reporting |
| Database | MySQL (Backend Validation & Data Integrity Testing) |
| Documentation | MS Excel (Test Cases, RTM, Bug Reports, Test Execution Reports) |
| Methodologies | SDLC/STLC (Software Development & Testing Life Cycle) |
| Version Control | Git & GitHub |
| Testing Types | Smoke Testing, Regression Testing, Functional Testing, Database Testing |
- Valid/Invalid email formats
- Password strength validation
- Mandatory field validation
- Duplicate account prevention
- Privacy policy acceptance
- Valid/Invalid credentials
- Session management
- "Remember Me" functionality
- Security validation
- Logout confirmation
- Email verification
- Reset link generation
- Password reset workflow
- Security token validation
- Profile information updates
- Password change functionality
- Newsletter subscription
- Account deletion
- Search functionality accuracy
- Empty search handling
- Special character validation
- Result count verification
opencart_ecommerce/
β
βββ π FRS/ # Functional Requirement Specifications
β βββ FRS_OpenCart_Ecommerce.xlsx
β βββ FRS_OpenCart_Ecommerce.pdf
β
βββ π Test_Cases/ # Comprehensive Test Cases
β βββ Register_Test_Cases.xlsx
β βββ Login_Test_Cases.xlsx
β βββ Logout_Test_Cases.xlsx
β βββ Forgot_Password_Test_Cases.xlsx
β βββ Account_Test_Cases.xlsx
β
βββ π RTM/ # Requirement Traceability Matrix
β βββ RTM_OpenCart.xlsx
β
βββ π Defect_Reports/ # Bug Reports & Defect Logs
β βββ Sample_Defect_Report.xlsx
β
βββ π Test_Execution_Reports/ # Test Execution Summary
β βββ Test_Execution_Report.xlsx
β
βββ π LICENSE # MIT License
βββ π README.md # Project Documentation
- β Functional Requirement Specifications (FRS)
- β Test Plan outlining scope, objectives, and approach
- β Test Strategy for each module
- β
25+ Detailed Test Cases with:
- Pre-conditions
- Test steps
- Expected results
- Actual results
- Pass/Fail status
- Priority & Severity classification
- β Complete mapping between requirements and test cases
- β 100% bidirectional traceability
- β Coverage analysis ensuring no gaps
- β
8+ Bug Reports documented with:
- Defect ID and summary
- Steps to reproduce
- Expected vs Actual behavior
- Screenshots/Evidence
- Severity and Priority
- Environment details
- Status tracking (New β Assigned β Fixed β Closed)
- β Smoke testing results
- β Regression testing summary
- β Test metrics and coverage statistics
- β Defect distribution analysis
Designed and executed 25+ comprehensive test cases covering:
- β Positive scenarios (Happy path testing)
- β Negative scenarios (Error handling)
- β Boundary value scenarios (Edge cases)
- β End-to-end user workflows
Result: Successfully identified 8+ functional defects across core modules with zero escapes to production.
Created and maintained a Requirement Traceability Matrix (RTM) ensuring:
- β 100% alignment between business requirements and test cases
- β Bidirectional traceability for impact analysis
- β Gap identification in requirement coverage
Result: Achieved 100% requirements coverage with full traceability.
Implemented comprehensive defect tracking:
- β Documented detailed bug reports with clear reproduction steps
- β Attached screenshots and supporting evidence
- β Classified defects by severity (Critical, Major, Minor, Trivial)
- β Tracked defects through complete lifecycle (Open β Assigned β Fixed β Verified β Closed)
Result: Ensured 100% resolution of all critical and major defects before production deployment.
Performed SQL-based backend testing using MySQL:
- β Verified user registration data persistence
- β Validated search result accuracy through database queries
- β Ensured data integrity across CRUD operations
- β Cross-verified UI data with database records
Result: Identified data inconsistencies between frontend and backend, ensuring data accuracy.
Executed comprehensive regression testing cycles:
- β Smoke Testing post-deployment to validate critical workflows
- β Regression Testing to ensure bug fixes didn't introduce new defects
- β Re-testing of fixed defects for verification
- β Impact analysis for code changes
Result: Reduced potential production issues by ensuring zero impact on existing functionality.
Utilized Git/GitHub for test artifact management:
- β Centralized repository for all test plans, cases, and scripts
- β Version control for test documentation
- β Collaborative review process for test artifacts
- β Change tracking and history maintenance
Result: Maintained organized, accessible, and traceable testing documentation.
- Microsoft Excel (for viewing test artifacts)
- PDF Reader (for FRS documents)
- MySQL Workbench (optional, for database validation review)
- Git (for cloning the repository)
git clone https://github.com/kishorekumarrasalay-02/opencart_ecommerce.git
cd opencart_ecommerceNavigate to the FRS/ folder to understand the application requirements:
cd FRS/
# Open FRS_OpenCart_Ecommerce.xlsx or .pdfNavigate to Test_Cases/ folder to review detailed test scenarios:
cd Test_Cases/
# Open individual test case files for each moduleEach test case includes:
- Test Case ID
- Test Scenario
- Pre-conditions
- Test Steps
- Test Data
- Expected Result
- Actual Result
- Status (Pass/Fail)
- Priority & Severity
Navigate to RTM/ folder to verify requirements coverage:
cd RTM/
# Open RTM_OpenCart.xlsxRTM provides:
- Requirement ID mapping to Test Case ID
- Coverage percentage
- Testing status for each requirement
Navigate to Defect_Reports/ folder to examine identified bugs:
cd Defect_Reports/
# Open Sample_Defect_Report.xlsxDefect reports include:
- Defect ID & Summary
- Steps to Reproduce
- Expected vs Actual Behavior
- Screenshots
- Severity & Priority
- Status & Resolution
Navigate to Test_Execution_Reports/ for overall testing metrics:
cd Test_Execution_Reports/
# Open Test_Execution_Report.xlsx| Metric | Count | Percentage |
|---|---|---|
| Total Test Cases | 25+ | 100% |
| Test Cases Executed | 25+ | 100% |
| Test Cases Passed | 17+ | ~68% |
| Test Cases Failed | 8+ | ~32% |
| Defects Identified | 8+ | - |
| Defects Fixed | 8+ | 100% |
| Requirements Covered | All | 100% |
| Regression Cycles | 2+ | - |
User Registration: ββββββββββββββββββββ 80%
Login/Logout: ββββββββββββββββββββ 95%
Password Recovery: ββββββββββββββββββββ 85%
Account Management: ββββββββββββββββββββ 80%
Product Search: ββββββββββββββββββββ 90%
| Severity | Count | Percentage |
|---|---|---|
| π΄ Critical | 1 | 12.5% |
| π Major | 3 | 37.5% |
| π‘ Minor | 3 | 37.5% |
| π’ Trivial | 1 | 12.5% |
Test Case ID: TC_REG_001
Module: User Registration
Priority: High | Severity: Critical
Test Scenario: Verify user registration with valid credentials
Pre-conditions:
- Application is accessible
- Database is connected
Test Steps:
1. Navigate to Registration page
2. Enter valid First Name
3. Enter valid Last Name
4. Enter valid Email address
5. Enter valid Password (8+ chars, mixed case)
6. Confirm Password
7. Accept Privacy Policy
8. Click "Continue"
Expected Result:
- User should be successfully registered
- Confirmation message displayed
- Redirect to "My Account" page
- User data saved in database
Actual Result: As Expected
Status: β
PASS
Defect ID: BUG_001
Summary: Password field accepts less than 4 characters
Module: User Registration
Severity: Major | Priority: High
Steps to Reproduce:
1. Go to Registration page
2. Enter password with 3 characters "abc"
3. Submit the form
Expected Result:
Error message: "Password must be at least 4 characters"
Actual Result:
User is registered successfully with 3-character password
Environment: Chrome 120.0, Windows 11
Status: Fixed & Verified
- β Manual Testing Expertise - Comprehensive test case design and execution
- β SDLC/STLC Knowledge - Understanding of complete software testing lifecycle
- β Defect Life Cycle Management - From identification to closure
- β SQL & Database Testing - Backend validation and data integrity checks
- β Test Documentation - Professional test artifacts creation
- β Requirement Analysis - RTM creation and traceability management
- β Version Control - Git/GitHub for test repository management
- β Attention to Detail - Identification of edge cases and boundary scenarios
- β Analytical Thinking - Root cause analysis and defect investigation
This project is licensed under the MIT License - see the LICENSE file for details.
Kishore Kumar R
π Mobile: +91-9490946159
π§ Email: kishorekumarrasalay05@gmail.com
πΌ LinkedIn: linkedin.com/in/kishorekumarrasalay
π GitHub: github.com/kishorekumarrasalay-02
Special thanks to:
- OpenCart community for the e-commerce platform
- Testing community for best practices and methodologies
- Peers and mentors for valuable feedback