A professional Manual Testing Project developed for the TutorialsNinja Demo Application to demonstrate the complete Manual Software Testing Life Cycle (STLC).
This project covers requirement analysis, test planning, test scenario design, manual test case creation, test data preparation, requirement traceability, defect reporting, test execution, and test summary reporting.
The project has been designed to simulate real-world QA documentation and complements the Hybrid Selenium Automation Framework developed for the same application.
The primary objective of this project is to validate the core functionalities of the TutorialsNinja Demo Application through comprehensive manual testing and prepare stable automation candidates for the Hybrid Automation Framework.
- Application: TutorialsNinja Demo Application
- URL: https://tutorialsninja.com/demo/
- Testing Type: Manual Functional Testing
- Environment: Demo / QA
- Browser: Google Chrome
- Operating System: Windows 11
- User Registration
- User Login
- Product Search
- Logout
- Forgot Password
- Wishlist
- Shopping Cart
| Metric | Count |
|---|---|
| Test Scenarios | 8 |
| Manual Test Cases | 32 |
| Test Data Sets | 13 |
| Defects Reported | 1 |
| Passed | 30 |
| Failed | 1 |
| Blocked | 1 |
| Pass Percentage | 93.75% |
TutorialsNinja-Manual-Testing
│
├── Test Plan.docx
├── Test Scenarios.xlsx
├── Manual Test Cases.xlsx
├── Test Data.xlsx
├── Requirement Traceability Matrix.xlsx
├── Bug Report.xlsx
├── Test Execution Report.xlsx
├── Test Summary Report.docx
├── Screenshots/
└── README.md
Defines the testing strategy, scope, objectives, environment, entry/exit criteria, risks, and deliverables.
Contains high-level functional scenarios covering the application's major business workflows.
Includes detailed positive, negative, and validation test cases with preconditions, test steps, expected results, and execution status.
Contains reusable datasets used across multiple test cases.
Maps business requirements to corresponding test scenarios and manual test cases.
Documents the defect identified during testing using an industry-standard defect reporting format.
Records the execution status of representative manual test cases.
Provides the overall testing outcome, execution metrics, defect summary, and recommendations.
One defect was identified during testing.
| Bug ID | Module | Severity | Status |
|---|---|---|---|
| BUG_001 | Logout | Low | Open |
Description
After logging out, the browser Back button allows the user to view previously visited authenticated pages. Although no authenticated actions can be performed and the application redirects to the Login page when an action is attempted, the previously viewed page remains visible due to browser caching/session handling.
Requirement Analysis
↓
Test Planning
↓
Test Scenario Design
↓
Test Case Design
↓
Test Data Preparation
↓
Test Execution
↓
Bug Reporting
↓
Test Summary
This Manual Testing Project is directly aligned with the TutorialsNinja Hybrid Automation Framework.
The validated manual test cases served as automation candidates for Selenium automation, demonstrating the transition from manual testing to automated regression testing.
- Microsoft Excel
- Microsoft Word
- Google Chrome
- Git
- GitHub
- Add Cross-Browser Testing
- Integrate API Testing
- Add Performance Testing
- Add Security Testing
- Execute Regression Testing after defect fixes
- Expand test coverage with additional edge cases
Abhidept Singh
QA Engineer | Manual Testing | Selenium Automation | Java | TestNG | Maven | Git | GitHub
➡️ TutorialsNinja Hybrid Automation Framework
This project demonstrates how the validated manual test cases from this repository were automated using Selenium WebDriver, Java, TestNG, Maven, Apache POI, Extent Reports, and Jenkins.