-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
chore: Split cypress tests locally #5925
Conversation
|
✅ Deploy Preview for mermaid-js ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
commit: |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #5925 +/- ##
=======================================
Coverage 4.67% 4.67%
=======================================
Files 372 372
Lines 51669 51669
Branches 611 611
=======================================
Hits 2414 2414
Misses 49255 49255
Flags with carried forward coverage won't be shown. Click here to find out more. |
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
It also works locally, I tested this by running:
concurrently \
'SPLIT=4 SPLIT_INDEX=0 SPLIT_FILE=cypress/timings.json cypress run' \
'SPLIT=4 SPLIT_INDEX=1 SPLIT_FILE=cypress/timings.json cypress run' \
'SPLIT=4 SPLIT_INDEX=2 SPLIT_FILE=cypress/timings.json cypress run' \
'SPLIT=4 SPLIT_INDEX=3 SPLIT_FILE=cypress/timings.json cypress run'
And I managed to cut down the E2E test time from ~20 minutes to ~7 minutes.
Co-authored-by: Alois Klink <[email protected]>
📑 Summary
Avoids the dependency on the cypress server, so tests from forks can also run in parallel.
📏 Design Decisions
Describe the way your implementation works or what design decisions you made if applicable.
📋 Tasks
Make sure you
MERMAID_RELEASE_VERSION
is used for all new features.pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.