Skip to content
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

Add E2E tests for IBC between Anoma chains #79

Closed
9 tasks done
yito88 opened this issue Feb 16, 2022 · 2 comments · Fixed by #296
Closed
9 tasks done

Add E2E tests for IBC between Anoma chains #79

yito88 opened this issue Feb 16, 2022 · 2 comments · Fixed by #296

Comments

@yito88
Copy link
Member

yito88 commented Feb 16, 2022

We need E2E tests to verify the IBC operations on Anoma.

This task focuses on the verification for IBC between two Anoma chains without a relayer.

Test targets

  • Client
    • Create, update
  • Connection
    • Handshake to open a connection
  • Channel
    • Handshake to open a channel
    • Close a channel
    • Close a channel due to timeout
  • ICS20 Token transfer
    • Token transfer (escrow/unescrow/mint/burn)
    • Refund due to timeout or ack failure
    • Transfer via the third chain (Chain A -> Chain B -> Chain C)
    • Transfer back via the thrid chain (Chain C -> Chain B -> Chain A)
@yito88 yito88 self-assigned this Feb 16, 2022
@tzemanovic tzemanovic transferred this issue from anoma/anoma Jul 7, 2022
@tzemanovic tzemanovic mentioned this issue Aug 8, 2022
@yito88 yito88 mentioned this issue Aug 10, 2022
29 tasks
@cwgoes
Copy link
Collaborator

cwgoes commented Jan 12, 2023

@yito88 what is the status of this?

@yito88
Copy link
Member Author

yito88 commented May 12, 2023

@yito88 yito88 closed this as completed May 12, 2023
@github-project-automation github-project-automation bot moved this from Todo to Tested in Devnet in Namada-Old May 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Tested in Devnet
Development

Successfully merging a pull request may close this issue.

2 participants