XNet message integration testing plan

[cryptoAtwill]

A list of test case for cross network messaging integration testing:

FUND

fund_native_works: Action: Sender in the parent sends some fund to another address in the child. Expected:

• Address in the child observes the balance increased.
• Child circulation increases
• fund_native_fails: Action: Sender in the parent sends some fund to a contract address with no receive nor fallback in the child. Expected:
  • Address in the child does not observe an increase in the balance.
  • A Transfer failed receipt will be attached to the xnet fund message.
  • Bottom up message for returning the fund is created.
  • Fund returned back to the sender if bottom up checkpoint submission is enabled.
  • Child circulation does not change
• fund_erc20_works: Action: Sender in the parent sends some erc20 token to another address in the child. Expected:
  • Address in the child observes the balance increased.
  • Child circulation increases
• fund_erc20_fails: Action: Sender in the parent sends some erc20 token to a contract address with no receive nor fallback in the child. Expected:
  • Address in the child does not observe an increase in the balance.
  • A Transfer failed receipt will be attached to the xnet fund message.
  • Bottom up message for returning the fund is created.
  • Fund returned back to the sender if bottom up checkpoint submission is enabled.
  • Child circulation does not change

Release

• release_native_works: Action: Sender in the child subnet sends some fund to another address in the parent. Expected:
  • Address in the parent observes the balance increased.
  • Child circulation decreases.
• release_native_fails: Action: Sender in the child sends some fund to a contract address with no receive nor fallback in the parent. Expected:
  • Address in the parent does not observe an increase in the balance.
  • A Transfer failed receipt will be attached to the xnet release message.
  • Top down message for returning the release is created.
  • Fund returned back to the sender
  • Child circulation does not change
• release_native_works_no_fund: Action: Sender does not go through fund from the parent. Someone else has funded the sender in the child subnet. Sender in the child subnet sends some fund to another address in the parent. Expected:
  • Address in the parent observes the balance increased.
  • Child circulation decreases
• release_erc20_works: Action: Sender in the child subnet sends some fund to another address in the parent. Parent's supply source is erc20. Expected:
  • Address in the parent observes the erc20 balance increased.
  • Child circulation decreases
• release_erc20_fails: Action: Sender in the child sends some fund to an address blocked by the erc20 address. Expected:
  • Address in the parent does not observe an increase in the balance.
  • A Transfer failed receipt will be attached to the xnet release message.
  • Top down message for returning the release is created.
  • Fund returned back to the sender
  • Child circulation does not change

Call

• call_with_native_value_works: Action: Caller in the parent calls some another contract in the child with some native value. Expected:
  • Contract call success with success receipt
  • Child circulation increases
• call_with_native_value_fails: Action: Caller in the parent calls some another contract in the child with some native value that reverts. Expected:
  • Contract call success with the corresponding failed receipt
  • Child circulation does not change
• call_with_erc20_works: Action: Caller in the parent calls some another contract in the child with some erc20 value. Expected:
  • Contract call success with success receipt
  • Child circulation increases
• call_with_erc20_fails: Action: Caller in the parent calls some another contract in the child with some erc20 value that reverts. Expected:
  • Contract call success with the corresponding failed receipt
  • Child circulation does not change
  • Erc20 returns back to the caller

### Tasks

[linear[bot]]

ENG-617 XNet message integration testing plan

[dnkolegov]

I think that tests that touch the subnet circulation supply somehow are not possible to implement within the MultiSubnet test framework with the current actors API. For example, release_native_works_no_fund suggests that the circulation supply of the child subnet is changed, but the Solidity contract does not have API for that, except fund, which should not be used here according to the test case.

[cryptoAtwill]

I have tested a one node setup for fund and release with native token. They are working. The issues with current code base is, it's extremely difficult to debug and visualise the Receipt state and making xnet contract calls. I create issues to write tool for such functions.