Repository navigation
feat(e2e): add java-tron local node configuration - #44149
Conversation
✨ Files requiring CODEOWNER review ✨🧪 @MetaMask/qa (1 files, +494 -0)
|
Builds ready [e56d7e4]
⚡ Performance Benchmarks (Total: 🟢 16 pass · 🟡 8 warn · 🔴 0 fail)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
e56d7e4 to
7af8393
Compare
b8bb32c to
076f057
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
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 [7af8393]
⚡ Performance Benchmarks (Total: 🟢 15 pass · 🟡 9 warn · 🔴 0 fail)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
7af8393 to
b493fb2
Compare
|
| "webpack:lavamoat:policy:mv2": "concurrently 'yarn webpack:lavamoat:build:mv2 --generatePolicy' 'yarn webpack:lavamoat:build:mv2 --generatePolicy --type flask' 'yarn webpack:lavamoat:build:mv2 --generatePolicy --type beta' 'yarn webpack:lavamoat:build:mv2 --generatePolicy --type experimental' --kill-others-on-fail", | ||
| "webpack:lavamoat:policy:mv3": "concurrently 'yarn webpack:lavamoat:build --generatePolicy' 'yarn webpack:lavamoat:build --generatePolicy --type flask' 'yarn webpack:lavamoat:build --generatePolicy --type beta' 'yarn webpack:lavamoat:build --generatePolicy --type experimental' --kill-others-on-fail", | ||
| "foundryup": "yarn mm-foundryup", | ||
| "java-tron": "node_modules/.bin/java-tron", |
There was a problem hiding this comment.
could you please explain the purpose of each new scripts for tron ?
There was a problem hiding this comment.
The idea of this script is to be a Tron equivalent to foundryup. It uses a package to manage a local Java Tron node that is started to power our E2E tests instead of mocking everything
There was a problem hiding this comment.
I am curios why its 3 new scripts: java-tron, java-tron-up, java-tron-up:install
There was a problem hiding this comment.
Ah, yeah actually now that I think about it the install one is not really needed. It's syntactic sugar for java-tron-up passing an install parameter
Builds ready [b493fb2]
⚡ Performance Benchmarks (Total: 🟢 17 pass · 🟡 7 warn · 🔴 0 fail)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|



Description
This PR adds the java-tron local node configuration, the supporting package scripts, and a
jest.configignore entry so the node config assets are excluded from unit runs. It is one reviewable step of a linear stack and configures (but does not yet boot) the Tron local node. It replaces the base commit of the earlier #44141. Based on a freshmainand under 1000 changed lines.Changelog
CHANGELOG entry: null
Related issues
Part of the local-blockchain E2E initiative (WPN-536).
Replaces the base of #44141.
Manual testing steps
yarn installyarn jestdoes not attempt to collect the ignored config assets.Screenshots/Recordings
N/A — test infrastructure only, no user-facing UI change.
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Low Risk
Test-only infrastructure and lockfile changes; no wallet, auth, or production runtime behavior.
Overview
Adds local java-tron support for upcoming Tron E2E work: dev dependency
@metamask/java-tron-up, yarn scripts (java-tron,java-tron-up,java-tron-up:install), andtest/e2e/seeder/tron/java-tron-config.tsexportingcreateJavaTronPrivateNetworkConfig()to emit private-net HOCON with a runtimefullNodePortoverride (P2P disabled vialisten.port = 0, discovery off).Jest gains
modulePathIgnorePatternsfor.metamask/cache/java-tron-up/so cached installer assets are not picked up by unit runs. This step configures the node template only; it does not start or wire aTronNodeyet.Reviewed by Cursor Bugbot for commit b493fb2. Bugbot is set up for automated code reviews on this repo. Configure here.