feat: add E2E CI and harden Docker build migrations#1377
Conversation
|
@AnishSarkar22 is attempting to deploy a commit to the Rohan Verma's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
… backend and Celery worker
…nd add readiness check
… and updating test command
…in alembic migrations for idempotency
…g columns and indexes before creation
…kflow for backend and Redis services
…ction versions and improve build targets
…nhance E2E testing environment
…on and updating Docker Compose for backend build reference
…ne dependency management
…thentication flow
…add shared volume for backend services
…dating environment variables for Google OAuth
…ree models for comprehensive E2E testing
… to negative values for improved test isolation
…lated directories and files for improved E2E testing
…ndency management
Description
docker-build.ymlwith updated action versionsffmpegdep in backend dockerfilepnpm-workspace.yamlforallowBuildsfeature.biome.jsonto add additional test-related directories and filesMotivation and Context
FIX #
Screenshots
API Changes
Change Type
Testing Performed
Checklist
High-level PR Summary
This PR introduces a GitHub Actions workflow for end-to-end testing using Playwright. The workflow sets up a complete testing environment with PostgreSQL (pgvector), Redis, a FastAPI backend, Celery workers, and the Next.js frontend. It includes sophisticated service orchestration with custom E2E entrypoints that hijack
sys.modulesto replace real external API calls (Composio, OpenAI, Anthropic) with fakes, uses sentinel API keys to prevent accidental real API calls, and configures proxy settings to block external HTTP traffic except for HuggingFace model downloads. The workflow runs on pull requests to main/dev branches when relevant paths change and includes comprehensive health checks, caching strategies for dependencies and models, and artifact uploads for test reports and logs.⏱️ Estimated Review Time: 15-30 minutes
💡 Review Order Suggestion
.github/workflows/e2e-tests.yml