Skip to content
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

Closed
wants to merge 17 commits into from

Conversation

nihal467
Copy link
Member

@nihal467 nihal467 commented Oct 8, 2024

Proposed Changes

  • Fixes #issue_number
  • Change 1
  • Change 2
  • More?

@ohcnetwork/care-fe-code-reviewers

Merge Checklist

  • Add specs that demonstrate bug / test a new feature.
  • Update product documentation.
  • Ensure that UI text is kept in I18n files.
  • Prep screenshot or demo video for changelog entry, and attach it to issue.
  • Request for Peer Reviews
  • Completion of QA

Copy link

netlify bot commented Oct 8, 2024

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit e9c607f
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/6705070d2c71750008289e31
😎 Deploy Preview https://deploy-preview-8738--care-ohc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

cloudflare-workers-and-pages bot commented Oct 8, 2024

Deploying care-fe with  Cloudflare Pages  Cloudflare Pages

Latest commit: e9c607f
Status: ✅  Deploy successful!
Preview URL: https://9348209b.care-fe.pages.dev
Branch Preview URL: https://cypress-action.care-fe.pages.dev

View logs

@nihal467
Copy link
Member Author

nihal467 commented Oct 8, 2024

Conclusion:
Due to GitHub Actions' sequential job structure, the current remaining approach would be is to run the setup in one runner, expose the services via Cloudflare/ngrok, and have another runner connect and run parallel Cypress tests.

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]

@nihal467 nihal467 closed this Oct 8, 2024
@nihal467 nihal467 self-assigned this Oct 8, 2024
@rithviknishad rithviknishad deleted the cypress-action branch December 2, 2024 03:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant