Skip to content

🧪 SSR Production Validation Sprint #39

@Alessandro100

Description

@Alessandro100

Objective

Conduct a coordinated, team-wide validation of the SSR MobilityDatabase before production cutover. Time box: 2:30 hours

Goal: Identify functional, UX, browser, performance, SEO, caching, and routing regressions under real-world usage.

This issue is the coordination hub.
All bugs must be logged as separate issues.

Browsers To Test

Desktop (Priority)

  • Chrome (latest)
  • Safari (latest)
  • Firefox
  • Edge

Mobile

  • iOS Safari
  • Android Chrome (if available)

Screen Sizes

  • Desktop (1440px+)
  • Laptop (~1280px)
  • Tablet
  • Mobile (375px)

Themes

  • light
  • dark

Bug Reporting Rules

If you find an issue:

  1. Create a new GitHub issue
  2. Title format [Browser][Screen] Short description (ex: [Safari][Mobile] Map markers not rendering)
  3. Add proper label: "launch-blocker" "launch-high" "launch-medium" "launch-cosmetic"
  4. Include:
  • Steps to reproduce
  • Expected behavior
  • Actual behavior
  • Browser + screen size (if applicable)
  • Screenshot or recording
  1. Link it back to this issue. (Related to #x)

Severity Definitions

launch-blocker

  • Breaks core flow
  • Incorrect data
  • Auth failure
  • Major SEO regression
  • Production unsafe

launch-high

  • Important UX failure
  • Major layout break
  • Performance regression

launch-medium

  • Noticeable but not blocking

launch-cosmetic

  • Minor UI polish issue

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedWhen a ticket cannot be started until another ticket / process is completed

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions