-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
E2E tests #26
E2E tests #26
Conversation
LGTM, going to refresh reviews |
messages/teleporter/message.go
Outdated
func UnpackMessageReceivedResult(result []byte) (bool, error) { | ||
var success bool | ||
err := EVMTeleporterContractABI.UnpackIntoInterface(&success, "messageReceived", result) | ||
return success, err | ||
} | ||
|
||
// PackSendCrossChainMessageEvent packs the SendCrossChainMessage event type. PackEvent is documented as not supporting struct types, so this should be used | ||
// with caution. Here, we only use it for testing purposes. In a real setting, the Teleporter contract should pack the event. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make this warning a little more obvious? Maybes start one line of the comment with "CAUTION". I would totally miss this most of the time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call, clarified that. I also thought about moving it to package tests
, but that unfortunately creates an import cycle. If we decide to move these Teleporter packing/unpacking utils to teleporter
, we can spend more energy putting up better guardrails, but IMO a more explicit comment is sufficient for now.
a4d2cf5
Why this should be merged
Provides an e2e test that makes sure the relayer is running properly from start up, subscribing, and delivering the message to destination chain and address. Fixes #15
How this works
sendWarpMessage
with a Teleporter message payloadThis can be extended for other future message protocols we support.
How this was tested
CI, unit tests, locally
How is this documented
README