Client » PQS_Japan

Module:¶

• User Profile / Authentication / UI

Today's QA Activities & Findings¶

1. UI Flicker on Page Load

   • During page load, a pink background flashes momentarily before the default profile image is displayed, causing a noticeable visual flicker.

2. Redundant Navigation Options

   • The User Profile dropdown in the navbar contains both "Edit Profile" and "Settings" buttons that navigate to the same URL and perform identical actions, resulting in redundant UI elements.

3. Persistent Loading Indicator

   • On the Profile Dashboard, the checkmark icon remains visible even after the "Update Notifications" button has completed loading.

4. Layout Break with Large Input Values

   • Entering large strings in the Name and Email fields causes the page layout to break and overflow.

5. UX Enhancement Suggestion

   • Adding a hover effect to the "Favorites" icon would improve user experience by providing immediate visual feedback.

6. Critical Security Bug – Password Change

   • The "Current Password" field is non-functional. Users are able to change their password even after entering an incorrect current password.

7. Email Verification Flow

   • During sign-up, a verification link is sent to the user’s inbox. Clicking the "Verify Email" button opens the confirmation page within the same browser tab.

8. Severe Validation & Security Vulnerabilities

   • The form lacks proper validation, exposing the system to:
     • DDoS attacks
     • Cross-Site Scripting (XSS)
     • HTML injection
     • Malicious PHP file uploads
   • Critical Issue: Input payloads are rendered directly in the email output, posing a major security risk.

9. Form State Handling Issue

   • After a successful form submission, the form does not clear its data, leading to potential duplicate submissions and poor UX.

File¶

Issue Sheet
Drive Link

Task Overview¶

Today’s primary focus was on issue tracking, UI validation, and functional testing for PQSJapan Sprint 04. All identified issues were documented and tracked using Redmine, ensuring proper visibility and traceability for the development team.

Activities Performed¶

1. Issue Identification & Documentation¶

• Reviewed all assigned features and changes under Sprint 04
• Identified UI inconsistencies, functional bugs, and usability issues
• Logged all discovered issues in Redmine with:
  • Clear titles and descriptions
  • Proper severity and priority levels
  • Steps to reproduce
  • Expected vs actual results
  • Relevant screenshots where applicable

2. UI Testing¶

• Verified UI elements against design and requirement specifications
• Checked:
  • Layout alignment and responsiveness
  • Button placements and visibility
  • Font consistency and color usage
  • Form field validation messages
• Ensured a consistent and user-friendly interface across tested screens

3. Functional Testing¶

• Tested core functionalities related to Sprint 04 features
• Validated:
  • User interactions and workflows
  • Form submissions and input handling
  • Navigation and redirection behavior
  • Error handling and edge cases
• Confirmed that implemented functionalities behave as expected according to requirements

Tools Used¶

• Redmine – Issue tracking and sprint management
• Web Browser (Manual Testing) – UI and functional validation

Outcome¶

• All issues related to PQSJapan Sprint 04 were successfully listed in Redmine
• UI and functional testing completed for assigned modules
• Provided clear and actionable feedback to support faster bug fixing and sprint completion

Status¶

✅ Completed