QA PORTFOLIO

Bug Tracking Examples

Examples of how I find, document and verify defects.

High Severity CASE 01

Login Bug: HTML Injection In Email Field

During negative testing of the login page, I found that the email field accepted HTML input and the application did not handle it safely.

Steps to reproduce

  1. Open the login page.
  2. Enter <h1>test</h1> into Email field.
  3. Enter any password.
  4. Click Login.
  5. Check UI response, Network tab and API response.

Expected: Input is sanitized and validation error is displayed.

Actual: HTML is rendered in UI or payload reaches backend without filtering.

Impact: Weak validation / possible security issue.

Jira Summary: Login form renders HTML input from Email field. Type: Bug Area: Security / Validation Priority: High Environment: Chrome, Windows 11 Attachments: Screenshot, DevTools Network, API response
Medium Severity CASE 02

API Bug: Incorrect Status Code For Invalid Login

During REST API testing, I checked how the authentication endpoint handles invalid credentials.

Steps to reproduce

  1. Open Postman.
  2. Send POST request to /api/login.
  3. Use invalid email and password.
  4. Check status code and response body.

Expected: API returns 401 Unauthorized with clear error message.

Actual: API returns 200 OK with success:false or 500 Internal Server Error.

Impact: Incorrect API response handling.

Jira Summary: Invalid login returns incorrect API status code. Type: Bug Area: REST API / Authentication Priority: Medium Environment: Postman Attachments: Request body, response screenshot
High Severity CASE 03

Database Bug: Incomplete User Record

During registration testing, I validated that user data is saved correctly in the database after successful registration.

Steps to reproduce

  1. Register a new user through UI.
  2. Check API response.
  3. Run SQL query for the created email.
  4. Verify required fields: status and created_at.

Expected: User exists with valid status and created_at value.

Actual: User is created, but status or created_at is NULL.

Impact: Data integrity issue.

Jira Summary: Registration creates user with incomplete database fields. Type: Bug Area: Database / Registration Priority: High Environment: Web app, SQL client Attachments: SQL query result, API response
High Severity CASE 04

Client-Server Bug: UI Shows Success After Backend Error

During profile update testing, I found that the frontend showed a successful save message even when the backend request failed.

Steps to reproduce

  1. Open Profile Settings.
  2. Change user name.
  3. Click Save.
  4. Check request in DevTools Network tab.

Expected: User sees error message if backend returns failure.

Actual: Backend returns 500, but UI shows “Saved successfully”.

Impact: Frontend/backend state mismatch.

Jira Summary: Profile page shows success despite backend failure. Type: Bug Area: Frontend / Backend Sync Priority: High Environment: Chrome, Windows 11 Attachments: UI screenshot, Network response
Medium Severity CASE 05

SQL Bug: UI Filter Shows Incorrect Records

During search/filter testing, I compared UI results with database data to verify that filtering works correctly.

Steps to reproduce

  1. Open Users page.
  2. Select filter: Active.
  3. Compare UI count with SQL query.
  4. Check whether inactive records are displayed.

Expected: UI displays only active records.

Actual: UI also displays archived or inactive records.

Impact: Incorrect filtering logic.

Jira Summary: Status filter displays records with incorrect status. Type: Bug Area: Search / Filtering Priority: Medium Environment: Web app, SQL client Attachments: Screenshot, SQL query result
Medium Severity CASE 06

Upload Bug: Error Visible Only In Server Logs

During file upload testing, I checked how the application handles invalid file type and oversized files.

Steps to reproduce

  1. Upload invalid file type or oversized file.
  2. Observe generic UI error or freeze.
  3. Check backend logs.
  4. Find exception or validation error in logs.

Expected: User-friendly validation message is displayed.

Actual: UI shows generic error and backend logs contain exception.

Impact: Missing file validation / poor error handling.

Jira Summary: Invalid upload causes backend exception and poor UI error. Type: Bug Area: File Upload / Logs Priority: Medium Environment: Web app, Linux logs Attachments: Screenshot, server log excerpt
High Severity CASE 07

Regression Bug: Password Reset Link Can Be Reused

During regression testing after release, I verified that password reset links expire after successful use.

Steps to reproduce

  1. Request password reset.
  2. Use reset link once.
  3. Try to use the same link again.
  4. Check API response.

Expected: Second attempt returns 400/410 link expired.

Actual: Same reset link can be used repeatedly.

Impact: Regression / security issue.

Jira Summary: Password reset link remains valid after first use. Type: Bug Area: Regression / Security Priority: High Environment: Web app, API Attachments: Steps, API response, retest notes