-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removed Cypress cloud parallelization from cloud to preserve resource #8738
Conversation
✅ Deploy Preview for care-ohc ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Deploying care-fe with Cloudflare Pages
|
…into cypress-action
Conclusion: Summary of Approaches We Tried: Initial Approach (All Tests in One Runner): Tried running backend, frontend, and Cypress tests in a single runner, but the time duration reaches 55+ minutes for test to complete Two-Job Approach (Split Setup and Tests): Separated the setup and Cypress test jobs, but GitHub Actions' sequential processing meant the Cypress tests couldn't start until the setup was fully done. Background Setup in One Job: Tried running backend and frontend in the background while starting Cypress tests in parallel, but since GitHub Actions run sequentially, the 6 parallel node for Cypress tests wouldn't start together while the background frontend and backend is running Exposing Backend/Frontend (Cloudflare/ngrok): Finally, we can used a separate runner for setup, exposing backend/frontend services via Cloudflare/ngrok, so Cypress tests could run in parallel without reinitializing the services by copying everything from the tunnel [haven't tried it] |
Proposed Changes
@ohcnetwork/care-fe-code-reviewers
Merge Checklist