setup 2 chains for development

[taitruong]

objectives:

• development on minimal 2 chains: Juno and Stargaze
• optional 3rd chain: Terra

Todo:

• evaluate ts-relayer for faster development
• if ts-relayer is feasible:
  • write shell scripts for each chain: start.sh and stop.sh
  • provide test examples for contract interaction (store, instantiate, execute and query on contract for chain A or B)
• if not feasible check whether local chain or test nets for chain A or B would be fine
• update README with how-to

[taitruong]

@tot-truong check #2 because in cw-ibc-demo repo it uses ts-relayer for integration tests. It also has scripts for starting and stopping scripts.

[taitruong]

Also check this repo out: https://github.com/confio/ibc-tests-ics20

[Art3miX]

This should be part of the #2 ibc template, so if we want to create a new ibc contract, we can use the template, and it will already have a test suite ready to write tests for that specific contract.

Ideally with a quick cargo commend (cargo integration-tests) that will run a script that handles ts-relayer and do the tests.

[taitruong]

I'd move at least start, stop scripts higher. Integration part makes sense for ibc template. By the way: this is answered via email reply ;).

⁣Get TypeApp for Android ​

On Sep 8, 2022, 00:00, at 00:00, Art3miX @.***> wrote:

This should be part of the #2 ibc template, so if we want to create a new ibc contract, we can use the template, and it will already have a test suite ready to write tests for that specific contract.

Ideally with a quick cargo commend (cargo integration-tests) that will run a script that handles ts-relayer and do the tests.

-- Reply to this email directly or view it on GitHub: https://github.com/arkprotocol/arkprotocol/issues/3#issuecomment-1239949355 You are receiving this because you authored the thread.

Message ID: @.***>

[Art3miX]

I'd move at least start, stop scripts higher. Integration part makes sense for ibc template. By the way: this is answered via email reply ;). ⁣Get TypeApp for Android ​ … On Sep 8, 2022, 00:00, at 00:00, Art3miX @.> wrote: This should be part of the #2 ibc template, so if we want to create a new ibc contract, we can use the template, and it will already have a test suite ready to write tests for that specific contract. Ideally with a quick cargo commend (cargo integration-tests) that will run a script that handles ts-relayer and do the tests. -- Reply to this email directly or view it on GitHub: #3 (comment) You are receiving this because you authored the thread. Message ID: @.>

Well yea, those should be in the scripts folder at the root, because they are "global" to run a chain, nothing to do with specific contract.

[Art3miX]

check #10 PR, I added the 2 chains from the demo, i don't think we should waste time on setting our own chains atm. But we probably should add more test chains in the future.

I think we can close this issue once the PR merged.

[Art3miX]

We have a testing with 2 chains, should be closed?

[tot-truong]

We have a testing with 2 chains, should be closed?

Yes, I think with all the relayer and IBC stuff you've been doing this is outdated