Manual test suite for an e-commerce web application — covering the full QA lifecycle from test planning through bug reporting.
Built to demonstrate real-world manual testing practices: test case design using BVA and Equivalence Partitioning, structured bug reports with reproduction steps, and organized test execution records in ISTQB format.
| Folder | Contents |
|---|---|
test-plan/ |
Test plan document — scope, objectives, approach, entry/exit criteria |
test-cases/ |
48 test cases across 5 modules — Login, Registration, Product Search, Cart, Checkout |
bug-reports/ |
12 bug reports — severity rated, reproduction steps, expected vs actual |
test-execution/ |
Test execution report — pass/fail results, coverage summary |
Target: Demo e-commerce application
URL: https://www.saucedemo.com
Type: Web application
Browsers tested: Chrome, Firefox, Safari
| Module | Test Cases | Bugs Found | Status |
|---|---|---|---|
| Login & Authentication | 10 | 3 | Done |
| User Registration | 8 | 2 | Done |
| Product Search & Filter | 10 | 3 | Done |
| Shopping Cart | 10 | 2 | Done |
| Checkout Flow | 10 | 2 | Done |
| Total | 48 | 12 | Complete |
- Boundary Value Analysis (BVA) — input field limits, quantity ranges
- Equivalence Partitioning (EP) — valid/invalid input classes
- Decision Table Testing — login combinations, promo code logic
- Exploratory Testing — session handling, concurrent tab behavior
| Severity | Count | Example |
|---|---|---|
| Critical | 2 | Checkout completes without payment details |
| High | 4 | Cart total miscalculates with discount codes |
| Medium | 4 | Search returns irrelevant results for special characters |
| Low | 2 | UI alignment breaks on Safari mobile |
- Test Management: TestRail (structure), Excel
- Bug Tracking: Jira
- Browser Testing: Chrome DevTools, BrowserStack
Each test case follows this format:
TC-ID | Unique identifier (e.g., TC-LOGIN-001)
Module | Feature area
Test Title | What is being tested
Priority | High / Medium / Low
Precondition | Setup required before test
Steps | Numbered steps to execute
Expected | What should happen
Actual | What actually happened (filled during execution)
Status | Pass / Fail / Blocked
Sirajul Islam — SQA Engineer
linkedin.com/in/siraajul · siraajul.com