-
Notifications
You must be signed in to change notification settings - Fork 221
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
test support: ibc bridge mocks for @agoric/orchestration #9572
Labels
enhancement
New feature or request
Comments
mergify bot
added a commit
that referenced
this issue
Jun 25, 2024
refs: #9449 ## Description Disables `@agoric/orchestration` tests in `packages/boot` that interact directly with Vows. _`EV` does not currently support vows, and these tests block efforts related to #9449._ For tests that are skipped and not deleted, I propose testing these paths after the completion of #9572. ### Testing Considerations Skips tests instead deleting them. Taking on some tech debt until #9572
What kinds of IBC messages do we need to simulate responses for?
Could we reuse the code from boot test to simulate responses? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
In unit testing flows for
@agoric/orchestration
, theEchoConectionKit
is used to mock network / ibc:agoric-sdk/packages/orchestration/test/supports.ts
Line 107 in bc3bc6b
agoric-sdk/packages/orchestration/test/network-fakes.ts
Lines 98 to 108 in ad29545
This limits our ability to fully test contracts - we need to be able to simulate responses from a remote IBC Connection to see how a contract handles them.
In boot tests, we mocked some
Bridge.DIBC
events using responses for sim chains:agoric-sdk/packages/boot/tools/supports.ts
Lines 358 to 406 in 42b2e7e
Description of the Design
Provide a similar entry point for IBC mocks in @agoric/orchestration unit testing.
Security Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
The text was updated successfully, but these errors were encountered: