chore: Perform comprehensive QA audit and bug reporting for Campus App

[MehmetBegun]

Description

This initiative involves a high-intensity Quality Assurance (QA) audit of the Campus App to identify, document, and categorize all detectable bugs within the Android and Backend ecosystems. A thorough testing phase is critical to ensure application stability and performance benchmarks are met before the next release cycle. Every identified issue must be logged with technical precision in the respective repository to facilitate rapid remediation and reduce technical debt.

---

Ownership, Deadline & Effort

• Team Owner: Engineering
• Individual Owner: @MehmetBegun
• Deadline: 2026-01-19 24:00 (end of day, explicitly stated)
• Estimated Effort: 1 hour

---

Deliverables

• Bug Backlog: Individual GitHub issues opened in the android or backend repositories for every discovered bug.
• QA Screen Recording: A complete video walkthrough of the testing process documenting reproduction steps and observed behaviors.
• QA Summary Report: A high-level overview of the app's current stability status based on the audit findings.

---

Scope

In Scope:

• Functional testing of all campus-specific features (e.g., maps, schedules, dining, notifications).
• Integration testing between the Android client and the Backend API.
• UI/UX audit for visual inconsistencies, responsiveness, and dark mode compliance.
• Validation of data persistence and user session management.
• Creation of structured bug reports including severity, steps to reproduce, and environment details.

Out of Scope:

• Writing automated unit or end-to-end test scripts.
• Fixing the identified bugs (this task is strictly for identification and reporting).
• Load or stress testing requiring external infrastructure setup.

---

Acceptance Criteria

• Every bug found is documented as a separate GitHub issue in the correct repository (android or backend).
• Each bug report includes "Steps to Reproduce," "Expected Behavior," and "Actual Behavior."
• A screen recording of the entire QA session is uploaded and linked to the primary task or repository.
• Testing covers at least 90% of the visible features in the Campus App.
• All critical and high-priority bugs are flagged with appropriate labels.

---

Domain-Specific Notes: Engineering

• Backend: Monitor server logs (e.g., using Logcat or specialized backend logging) during the QA process to catch 500-series errors that may not be apparent in the UI.
• Android: Test on at least one physical device or a high-fidelity emulator to observe real-world performance and transitions.
• Documentation: Ensure each bug report includes the app version and device model used during testing for accurate debugging.

---

Validation / Review Requirements

• Validation: Verification of the bug backlog and the completion of the screen recording.
• Required Reviewers: Engineering Lead or QA Manager.
• Definition of Done: All discovered bugs are logged, the recording is submitted, and the audit is completed within the 1-hour window.

---

Additional Context

• Target Repositories: campus-app-android, campus-app-backend