You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deploy a Ganache node on LocalNet to support E2E testing for the utility module. More specifically #869
Origin Document
#869 needs either A) addition of a endpoint+secret to the repo and deploying this pair as the servicer configuration, or B) a development/testing relay chain node, e.g. Ganache:
Goals
Automatic deployment of a test node, i.e. which allows setting accounts/balances/etc., as part of LocalNet deployment. This node's service URL should be accessible from all pods running on LocalNet.
Deliverable
Updated LocalNet configuration
Updated documentation detailing how this works with E2E tests.
Non-goals / Non-deliverables
Deploying an actual production-grade Ethereum (or any other relay chain) node.
General issue deliverables
Update the appropriate CHANGELOG(s)
Update any relevant local/global README(s)
Update relevant source code tree explanations
Add or update any relevant or supporting mermaid diagrams
Testing Methodology
Task specific tests or benchmarks: make ...
New tests or benchmarks: make ...
All tests: make test_all
LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md
k8s LocalNet: verify a k8s LocalNet is still functioning correctly by following the instructions here
Objective
Deploy a Ganache node on LocalNet to support E2E testing for the utility module. More specifically #869
Origin Document
#869 needs either A) addition of a endpoint+secret to the repo and deploying this pair as the servicer configuration, or B) a development/testing relay chain node, e.g. Ganache:
Goals
Deliverable
Non-goals / Non-deliverables
General issue deliverables
Testing Methodology
make ...
make ...
make test_all
LocalNet
is still functioning correctly by following the instructions at docs/development/README.mdk8s LocalNet
is still functioning correctly by following the instructions hereCreator: [@adshmh]
Co-Owners: [@okdas @Olshansk]
The text was updated successfully, but these errors were encountered: