Bug Bash - Onboarding

[jennifer-luo-dev]

Assigned To:

Overview

Users can now navigate through the site and access all major pages. Since the project has been built from a collection of tickets completed by different developers, several frontend and backend bugs naturally appeared along the way. This ticket focuses on identifying and resolving issues in the Onboarding Flow to improve stability, consistency, and user experience.

Task

Your task is to thoroughly review the Onboarding Flow and identify at least 5 substantial bugs. These may be UI inconsistencies, broken functionality, backend data issues, rendering errors, accessibility problems, interaction glitches, or unexpected console errors.

Once identified, fix each bug and ensure the page behaves consistently with expected product behavior and matches design system standards. Please reference the Figma to get a better understanding of what the site should look like. Then, get started!

Task Breakdown:

• Manually test all interactions in the Onboarding Flow.
• Identify a minimum of 5 noteworthy bugs
• Document each bug you discover in the PR description under a numbered list
• Implement fixes for each bug
• Test again after each fix to ensure no regressions
• Clean up unused console logs, unused imports, and orphaned code fragments to improve code quality

Potential Bug Ideas

Here are some things to get you thinking:

• How does it behave when resize?
• Do buttons look like they’re clickable when hover (arrow, recoloring)?
• Find points on site that don't match the Figma
  Use your imagination to break the code and fix it! Test backend and message us if you have questions!

To get you started, here are some bugs that you can look for:

• UI layout breaking on certain screen sizes
• Buttons or links not responding
• Incorrect or missing API data
• Crashes, unhandled exceptions, or console errors
• Missing loading states or spinners
• Inconsistent styling or spacing compared to Figma
• Forms not validating correctly
• Filters or dropdowns not behaving as expected

Here are things to keep in mind

• Bugs should be meaningful: cosmetic tweaks alone (e.g., “1px off alignment”) do not count unless they break usability.
• If you find more than 5 bugs, fix as many as feasible — extra fixes are appreciated.
• If a bug requires backend changes, coordinate with the backend logic appropriately and ensure correctness end-to-end.
• Match all components to our design system (spacing, typography, color usage).
• Make sure all state changes and data loads handle errors gracefully.
• Ensure the page works smoothly across mobile, tablet, and desktop breakpoints.

Resources

• Figma
  Please message Jennifer with questions on tickets, Amitav with bugs, and Fatima with design questions. Happy Coding!