Manual QA testing project for the BharatGo website, covering functional, usability, and reliability validation across core user flows.
As part of the BharatGo project, comprehensive manual testing was conducted to ensure the website's functionality, usability, and reliability. Key activities included:
- Test Case Design — Created detailed, structured test cases covering core functionalities such as user authentication, navigation, search, and payment processes, with coverage across positive, negative, and edge case scenarios.
- Bug Reporting — Identified and documented bugs using a systematic approach, including clear reproduction steps, screenshots, and severity levels. Collaborated closely with the development team to drive issues to resolution.
- Manual Test Execution — Validated user flows end-to-end to ensure a seamless user experience and confirm compliance with expected requirements and standards.
Core Objectives:
- Ensure critical user journeys (login, navigation, search, payment) work reliably across scenarios
- Catch functional and usability issues before release through structured, repeatable test case design
- Maintain clear, actionable bug reports that speed up developer triage and fixes
- Validate the website against expected functional and non-functional requirements
| Tool / Technique | Purpose |
|---|---|
| Manual Testing | Validating user flows and overall user experience |
| Test Case Design (Positive/Negative/Edge Case) | Structured functional coverage |
| Bug Tracking Tool (e.g., JIRA) | Logging, tracking, and prioritizing defects |
| Browser DevTools | Cross-checking UI behavior and reproducing issues |
| Screenshots / Screen Recording | Supporting evidence for bug reports |
This was a manual testing engagement rather than an automation framework, so there's no code to install or run. To reproduce or continue this testing effort:
-
Access the application
- Open the BharatGo website in a supported browser (Chrome/Firefox recommended).
-
Review test scenarios
- Refer to the test case documentation covering:
- User Authentication (login/signup, valid & invalid credentials)
- Navigation (menus, links, page transitions)
- Search (valid queries, empty results, special characters)
- Payment (successful transactions, failed transactions, edge amounts)
- Refer to the test case documentation covering:
-
Execute test cases
- Follow each test case's steps and expected results.
- Mark each as Pass/Fail and capture screenshots for any failures.
-
Log defects
- For any failed test case, raise a bug report including:
- Steps to reproduce
- Expected vs. actual result
- Screenshot/recording
- Severity/priority level
- For any failed test case, raise a bug report including:
-
Track resolution
- Follow up with the development team through the bug tracking tool until the issue is verified as fixed.
- Thorough scenario coverage — Test cases span positive, negative, and edge-case paths across authentication, navigation, search, and payments — not just the "happy path."
- Structured bug reports — Every reported defect includes clear reproduction steps, severity classification, and supporting screenshots, reducing back-and-forth with developers.
- Cross-functional collaboration — Worked directly with the development team to clarify issues and confirm fixes, closing the loop from discovery to resolution.
- Requirement compliance checks — Verified that implemented features matched expected functional and usability requirements before sign-off.
BharatGo Website
├── User Authentication
│ ├── Valid login
│ ├── Invalid credentials
│ └── Session handling
├── Navigation
│ ├── Menu links
│ └── Page transitions
├── Search
│ ├── Valid search queries
│ ├── Empty/No results
│ └── Special character handling
└── Payment
├── Successful transaction
├── Failed/declined transaction
└── Edge case amounts
Rahul Chandeshware GitHub: github.com/Rahulchandeshware