Repository navigation
ci: run rosetta e2e tests with test:e2e - #1696
Merged
Merged
Conversation
vechain/rosetta#98 removed the test:e2e:custom script. Its jest globalSetup now starts Rosetta with thor solo on the custom network, so test:e2e replaces it.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
libotony
approved these changes
Nov 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The Rosetta e2e job fails on every PR and master push since vechain/rosetta#98 (merged 2026-10-30). That PR removed the
test:e2e:customnpm script, and this workflow calls it:This PR calls
npm run test:e2einstead, as rosetta's own CI does.test:e2e:customwasTEST_NETWORK=custom jest. After "No Internet access" error on IOS app #98, jest'sglobalSetupstarts Rosetta with thor solo and sets the network tocustomitself.globalSetuprunsdocker composein the rosetta directory, so it merges ourdocker-compose.override.yml(thethor-builderstage). It also reuses the image from thedocker compose buildstep, because the image now has a fixed name (vechain-rosetta).Type of change
How Has This Been Tested?