Manual QA Testing | Test Cases & Bug Reporting
Faisal Iqbal
Overview
This portfolio case study demonstrates a practical manual QA workflow for an anonymized web application. It includes concrete test cases, execution results, regression status, and defect examples rather than only describing the QA process.
The material is presented as a portfolio demonstration of manual QA methodology and documentation practices, not as a named client engagement.
Test case design
The test suite covers authentication, dashboard validation, file management, search, profile, notifications, and logout workflows. Each test case records the module, scenario, preconditions, steps, test data, expected result, actual result, priority, and execution status.
Detailed test case examples
TC-001 — Valid login with correct credentials
Module: Authentication
Preconditions: User is registered and active
Steps:
Navigate to the login page
Enter valid username and password
Click Login
Test data: valid_user / valid_pass
Expected result: User is logged in and redirected to the dashboard
Actual result: As expected
Priority: High
Status: Passed
TC-002 — Login with invalid password
Module: Authentication
Preconditions: User is registered
Steps:
Navigate to the login page
Enter valid username and invalid password
Click Login
Test data: valid_user / invalid_pass
Expected result: Error message is displayed and login fails
Actual result: As expected
Priority: High
Status: Passed
TC-005 — Upload valid PDF file
Module: File Management
Preconditions: User is logged in and has upload permission
Steps:
Navigate to File Upload
Select a valid PDF file under 5 MB
Click Upload
Test data: sample.pdf (2 MB)
Expected result: File is uploaded successfully and listed in the grid
Actual result: As expected
Priority: High
Status: Passed
TC-006 — Upload invalid file type
Module: File Management
Preconditions: User is logged in
Steps:
Navigate to File Upload
Select an .exe file
Click Upload
Test data: malware.exe
Expected result: Validation message is shown for invalid file type
Actual result: As expected
Priority: Medium
Status: Passed
TC-007 — Upload file exceeding size limit
Module: File Management
Preconditions: User is logged in
Steps:
Navigate to File Upload
Select a file larger than 5 MB
Click Upload
Test data: large.pdf (10 MB)
Expected result: File-size validation error is displayed
Actual result: As expected
Priority: Medium
Status: Passed
Regression test matrix
ID | Module | Scenario | Test data | Expected result | Status |
|---|---|---|---|---|---|
TC-001 | Authentication | Valid login with correct credentials | valid_user / valid_pass | Redirect to dashboard | Passed |
TC-002 | Authentication | Login with invalid password | valid_user / invalid_pass | Error displayed; login fails | Passed |
TC-003 | Authentication | Login with locked account | locked_user / valid_pass | Account-locked message displayed | Passed |
TC-004 | Dashboard | Verify dashboard loads successfully | valid_user / valid_pass | Dashboard widgets and user details displayed | Passed |
TC-005 | File Management | Upload valid PDF file | sample.pdf (2 MB) | File uploaded and listed | Passed |
TC-006 | File Management | Upload invalid file type | malware.exe | Invalid-file-type validation displayed | Passed |
TC-007 | File Management | Upload file exceeding size limit | large.pdf (10 MB) | File-size error displayed | Passed |
TC-008 | Search | Search with valid keyword | Patient Name | Relevant results displayed | Passed |
TC-009 | Search | Search with no results | xyz123 | “No records found” displayed | Passed |
TC-010 | Profile | Update user profile information | 03001234567 | Profile updated and reflected | Failed |
TC-011 | Notifications | Verify notification appears for new record | N/A | New notification displayed correctly | Failed |
TC-012 | Report Export | Export report to Excel | N/A | Excel report exported successfully | Blocked |
Test execution results
A regression execution contained 42 test cases:
32 Passed — 76%
6 Failed — 14%
2 Blocked — 5%
2 Not Executed — 5%
The execution view also tracked module-level results, test data, expected versus actual behavior, execution timestamps, comments, and the tester responsible for each run.
Defect examples
The execution results exposed issues that were recorded for follow-up:
WEB-1248 — Profile update failure
Related test: TC-010
Expected: Profile changes are saved and reflected
Actual: Profile was not updated
Result: Failed
Action: Defect logged for investigation
WEB-1251 — Notification not received
Related test: TC-011
Expected: A new notification appears after creating a new record
Actual: Notification was not received
Result: Failed
Action: Defect logged for investigation
TC-012 — Report export blocked
Expected: Report exports successfully in Excel format
Actual: Export could not be completed
Result: Blocked
Reason: API dependency
QA workflow demonstrated
This case study demonstrates:
Requirements-oriented test scenario design
Positive, negative, and validation testing
Functional and regression coverage
Test-data preparation
Expected-versus-actual result tracking
Priority and status management
Defect identification and traceability
Retesting and release-readiness reporting
Portfolio artifacts
Supporting portfolio artifacts include a detailed test-case spreadsheet and a regression execution dashboard showing the test matrix, statuses, failures, blocked tests, and logged defects.
Like this project
Posted Oct 7, 2026
Manual QA portfolio case study with concrete test cases, execution results, regression coverage, and defect examples for an anonymized web application.
