Issue: Missing EventsData and UserData – Add Database Seed File

[TVW96]

Description

Summary

The current environment doesn't include seeded EventsData or UserData. This prevents developers from effectively visualizing new code changes across Frontend, Backend, and Database layers. Beforehand, new features were tested through Playwright testing suites with every new commit. This was/is working, but the validation does not always provide immediate visibility into how changes impact the live application or database state + were required to update the test suite with every new feature or new addition to existing features.

Important

A standardized database seed file is required to populate the database with representative test data so developers can reliably run and test the application without manually creating records.

Benefits of Seeding Data

• Provides a consistent development dataset across all team members.
• Improves onboarding speed for new developers.
• Eliminates the need for manual database entry during development.
• Enables dynamic visualization of live code changes across frontend and backend services.
• Allows developers to see UI and API behavior immediately when modifying code.
• Improves debugging and development feedback loops by validating changes against realistic data.
• Reduces reliance on test-only verification by enabling interactive development and testing.

Tasks

Tasks:

• Create a database seed file containing sample EventsData
• Add representative UserData records for testing user-related features
• Define relationships between seeded users and events where necessary
• Integrate the seed script into the development setup workflow
• Ensure the seed process works with the existing Postgres database container
• Document the command for running the seed file in the project README
• Verify event listings, event cards, and event detail pages render correctly using seeded data

Visual Aids

Note: No visual aids are required for this section.