test: use tsx for E2E tests instead of ts-node#25399
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Builds ready [e3b7c7a]
Page Load Metrics (54 ± 3 ms)
Bundle size diffs
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #25399 +/- ##
========================================
Coverage 65.38% 65.38%
========================================
Files 1382 1382
Lines 54765 54765
Branches 14367 14367
========================================
Hits 35807 35807
Misses 18958 18958 ☔ View full report in Codecov by Sentry. |
|
Fascinating, that's a significant improvement. I wonder how it's so much faster. I see that |
|
Missing release label release-12.0.0 on PR. Adding release label release-12.0.0 on PR and removing other release labels(release-12.1.0), as PR was cherry-picked in branch 12.0.0. |
Description
On my computer, it took 17 seconds just to launch Mocha for an E2E test. Not launch a browser, not start chromedriver/Ganache, not withFixtures. 17 seconds just to launch Mocha and do nothing. And on CircleCI, this 17 seconds happens thousands of times per workflow.
A lot of this time was taken by
ts-node, which has a very slow startup time. I switched to usingtsx, which is much much faster.CircleCI Insights on
developshowing about 16k credits per workflowCircleCI Insights on this branch showing about 12k credits per workflow
After this is merged and observed for a bit, it may make sense to rebalance some
parallelisminconfig.yml.Related issues
Manual testing steps
yarn test:e2e:single [TESTPATH] --browser=chromeScreenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist
Co-authored-by: David Murdoch 187813+davidmurdoch@users.noreply.github.com