7.75 Deploy to Staging and Run Smoke Tests

[flyblackbox]

7.75 Deploy to Staging and Run Smoke Tests

Summary

Deploy the updated TypeScript + Prisma backend to the staging environment using the new Docker and CI/CD configuration. Run automated and manual smoke tests to verify critical paths and readiness for production.

Tasks

• Trigger a staging deployment via the CI/CD pipeline or deployment tool
• Confirm the correct image/tag is deployed to staging
• Apply any required Prisma migrations in the staging environment
• Run automated smoke tests against staging:
  - Basic health check endpoints
  - Core GraphQL queries and mutations (auth, posts, comments, messaging)
  - Subscriptions (if staging supports WebSockets)
• Perform manual smoke tests:
  - Login and basic user flows
  - Create/read/update/delete content
  - Check notifications and presence/chat (if applicable)
• Monitor staging logs for errors or performance anomalies
• Record any issues and create follow-up tickets as needed
• Confirm staging is stable and consistent with expectations

Expected Behavior

The staging environment runs the new backend version with stable behavior across critical feature paths, providing confidence for production deployment.

Tech Notes

• Use staging-specific environment variables and databases to avoid impacting production data.
• Ensure observability (logs, metrics) is available for staging.

Acceptance Criteria

• Staging deployment succeeds with the updated backend
• Automated and manual smoke tests pass
• Staging logs show healthy operation during test traffic
• Any issues identified are documented and either fixed or tracked before production deployment

Test Instructions

1. Use CI/CD or deployment tooling to deploy the latest build to staging.
2. Run automated smoke tests (if scripted) and review results.
3. Manually walk through core application flows in staging.
4. Check logs, metrics, and error trackers (e.g., Sentry) for staging during and after tests.

Labels

backend deployment staging testing phase7