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

Rc/0.31.0 #614

Merged
merged 215 commits into from
Oct 11, 2023

Resolving issues with main. Accpting develop.

8a69ccb
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Merged

Rc/0.31.0 #614

Resolving issues with main. Accpting develop.
8a69ccb
Select commit
Loading
Failed to load commit list.
GitHub Actions / E2E report yarn test-sdk succeeded Oct 5, 2023 in 1s

E2E report yarn test-sdk ✔️

Tests passed successfully

✔️ e2eTests/reports/junit-6b1e7bc0-63be-11ee-a469-abcc5cf31a2e.xml

58 tests were completed in 1361s with 49 passed, 0 failed and 9 skipped.

Test suite Passed Failed Skipped Time
test/parallel/sdk.API.batch.test.ts 7✔️ 735s
test/parallel/sdk.API.getInfo.test.ts 16✔️ 279s
test/parallel/sdk.API.submitableExtrinsic.test.ts 9✔️ 735s
test/parallel/sdk.API.utils.test.ts 8✔️ 1011s
test/parallel/xyk-sdk.API.activateLiqudity.test.ts 2✔️ 603s
test/sequential/sdk.API.claimRewards.test.ts 7✔️ 1359s
test/sequential/xyk-SDK.nonce.test.ts 7✖️ 8s
test/xcm/skip.SDK.imbue.transfer.test.ts 2✖️ 9s

✔️ test/parallel/sdk.API.batch.test.ts

✔️ Check that when we are using SDK batch function and the first call finishes with error next call doesn't finish
✔️ Check that when we are using SDK batch function and the second call finishes with error first call finishes successful
✔️ Happy path - batch
✔️ WHEN call batchAll where one item is failed THEN all entire transactions will rollback and fail
✔️ Happy path - batchAll
✔️ WHEN call forceBatch where one item is failed THEN check completed and failed items
✔️ Happy path - forceBatch

✔️ test/parallel/sdk.API.getInfo.test.ts

✔️ getAmountOfTokensInPool return poolAmount AND in reverse list of token we recived equal result
✔️ check parameters of getInvestedPools function
✔️ check parameters of getLiquidityTokenIds function
✔️ check parameters of getPool function
✔️ check parameters of getPools function
✔️ check parameters of getTotalIssuance functions
✔️ check parameters of getChain function
✔️ check parameters of getNodeName function
✔️ check parameters of getNodeVersion function
✔️ check waitForNewBlock
✔️ check calculateMintingFutureRewards
✔️ check getAssetsInfo
✔️ check getLiquidityTokens
✔️ check getOwnedTokens
✔️ check getTokenInfo
✔️ sdk - filter deactivated pools on node

✔️ test/parallel/sdk.API.submitableExtrinsic.test.ts

✔️ activate some Liquidity using SDK THEN claim rewards THEN deactivate Liquidity
✔️ check claimRewards
✔️ check mintLiquidity
✔️ check burnLiquidity
✔️ check createPool
✔️ check multiswapBuyAsset
✔️ check multiswapSellAsset
✔️ check transferTokens
✔️ check transferAllTokens

✔️ test/parallel/sdk.API.utils.test.ts

✔️ GIVEN buyAsset WHEN operation is confirmed AND isMultiSwapAssetTransactionSuccessful THEN it returns true
✔️ GIVEN buyAsset WHEN operation is failed AND isMultiSwapAssetTransactionSuccessful THEN it returns false
✔️ GIVEN sellAsset WHEN operation is confirmed AND isMultiSwapAssetTransactionSuccessful THEN it returns true
✔️ GIVEN sellAsset WHEN operation is failed AND isMultiSwapAssetTransactionSuccessful THEN it returns false
✔️ GIVEN multiSwapBuy WHEN operation is confirmed AND isMultiSwapAssetTransactionSuccessful THEN it returns true
✔️ GIVEN multiSwapBuy WHEN operation is failed AND isMultiSwapAssetTransactionSuccessful THEN it returns false
✔️ GIVEN multiSwapSell WHEN operation is confirmed AND isMultiSwapAssetTransactionSuccessful THEN it returns true
✔️ GIVEN multiSwapSell WHEN operation is failed AND isMultiSwapAssetTransactionSuccessful THEN it returns false

✔️ test/parallel/xyk-sdk.API.activateLiqudity.test.ts

✔️ Given a user hame some liquidity token THEN he activate them THEN deactivate
✔️ Activate liquidity and claim rewards

✔️ test/sequential/sdk.API.claimRewards.test.ts

✔️ GIVEN an user has available some rewards in one pool WHEN claims all rewards THEN the user gets the rewards for that pool
✔️ GIVEN an user has available some rewards in two pools WHEN claims all rewards THEN the user gets the rewards for thats pools
✔️ GIVEN an user has available some rewards in two pools one deactivated WHEN claims all rewards THEN the user gets the rewards for thats pools
✔️ GIVEN an user has available some rewards in two “pools” one solo token, one pool WHEN claims all rewards THEN the user gets the rewards for thats pools
✔️ GIVEN a user that has available some rewards in ten pools max for automatically claiming WHEN claims all rewards THEN the user gets the rewards for thats pools
✔️ GIVEN a user has available some rewards in over ten pools WHEN claims all rewards THEN the error is received
✔️ GIVEN a user has available some rewards in over ten pools AND this user claims some pool manually WHEN claims all rewards THEN the user gets the rewards for all remaining pools

✔️ test/sequential/xyk-SDK.nonce.test.ts

SDK test - Nonce tests - user
  ✖️ SDK- Nonce management - user
  ✖️ SDK- Nonce management - user - parallel
  ✖️ SDK- Nonce management - user - future Tx-
  ✖️ SDK- Nonce management - Extrinsic failed
  ✖️ SDK- Nonce management - Using custom nonce
  ✖️ [BUG?] SDK- Nonce management - Transaction outdated
SDK test - Nonce tests - Errors
  ✖️ [BUG?] SDK- Nonce management - RPC Failure - Not enough balance

✔️ test/xcm/skip.SDK.imbue.transfer.test.ts

XCM tests for Mangata <-> imbue
  ✖️ SDK ROC - mangata transfer assets to imbue
  ✖️ SDK ROC - imbue transfer assets to mangata