Test Cases
In order to make CLV as secure and high performance multi-chain. There are lots of test cases have been made to support.
- 1.The CLV EVM should provide the same interface for balance transfer and query.
- 2.The balance transfer should run correctly and related balance updated.
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/blob/main/tests/test-balance.ts
- 1.The CLV EVM can return correct genesis block.
- 2.CLV EVM can support query block by number or hash.
- 3.The returned block should contain transactions and correct transaction root.
- 4.The newly generated block should has valid timestamp and includes previous block as parent
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/blob/main/tests/test-block.ts
The transaction receipt should contains correct bloom data
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/blob/main/tests/test-bloom.ts
- 1.Smart contract can be correctly created by CLV EVM.
- 2.Smart contract creation can return transaction hash.
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/blob/main/tests/test-contract.ts
- 1.CLV EVM should support the invoke of smart contract call.
- 2.The smart contract call should return expected result.
- 3.The smart contract call should fail in case of invalid parameters.
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/blob/main/tests/test-contract-methods.ts
- 1.CLV EVM should support estimation of gas fee.
- 2.The gas limit should decrease on next block if gas unused.
- 3.The estimated gas should be correct for smart contract creation or method call.
Test cases can be viewed here: https://github.com/clover-network/clover-sdk/blob/main/tests/test-gas.ts
- 1.CLV EVM should support correct nonce query.
- 2.CLV EVM should return the revert reason in case of failure.
- 3.CLV EVM should return a valid transaction receipt for a successful or failed transaction.
In order to test the full functionality of CLV EVM, we provide a script which can automatically deploy Uniswap on CLV for one-shot.
- 1.It can deploy Uniswap ERC20 token to CLV
- 2.It can deploy Uniswap V2 Factory smart contract to CLV
- 3.It can deploy WETH ERC20 token to CLV
- 4.It can deploy Uniswap V2 Router smart contract to CLV
- 5.It can deploy Multicall smart contract to CLV
Please find the cool script here: https://github.com/clover-network/clover-sdk/blob/main/tests/e2e-tests/test/test-uniswap.js
CLV EVM is based on Frontier, we find that the gas fee estimation under some cases may fail, such as nested smart contract call. CLV provides a binary search based solution to solve the problem. Please find the details here:
After the fix, CLV EVM can support all kinds of gas estimation correctly, please find the test case here: https://github.com/clover-network/clover-sdk/blob/main/tests/inner-contract-tests/test/test-inner-contract.js
CLV has a powerful dual-chain architecture, which will empower its users to build their decentralized apps and digital assets on one blockchain (CLV EVM powered) and take advantage of Polkadot chain on the other. Thus CLV account binding is very important, it enables users to do all the staffs under one unified account. Also the bound accounts can share the same balance, as well as the integration of the cool features on the dual-chain.
The related test cases can be found here: https://github.com/clover-network/clover-sdk/blob/main/tests/account-bind-tests/test-account-bind.js
In order to test the performance of CLV chain, test cases have been carried out both on EVM and CLV Parachain.
The EVM TPS tests can be found at: https://github.com/clover-network/clover-sdk/blob/main/tests/tps-tests/test-web3-tps.js
The CLV Parachain tests can be found at: https://github.com/clover-network/clover-sdk/blob/main/tests/tps-tests/test-polkadot-tps.js
Last modified 1yr ago