Bugfix/liq tokens mgx 434 v2 (#603) #214
This check has been archived and is scheduled for deletion.
Learn more about checks retention
GitHub Actions / E2E report yarn test-parallel-autocompound
succeeded
Sep 29, 2023 in 0s
E2E report yarn test-parallel-autocompound ✔️
✔️ e2eTests/reports/junit-7ced7260-5ee2-11ee-a6c1-ed5e9b38ae30.xml
31 tests were completed in 1860s with 31 passed, 0 failed and 0 skipped.
Test suite | Passed | Failed | Skipped | Time |
---|---|---|---|---|
test/parallel/xyk-pallet.API.accuracy.shared.pool.test.ts | 5✔️ | 1343s | ||
test/parallel/xyk-pallet.API.parachainStacking.activateRewards.test.ts | 1✔️ | 191s | ||
test/parallel/xyk-pallet.API.pool.deactivated.test.ts | 2✔️ | 359s | ||
test/parallel/xyk-pallet.API.pool.promoting.test.ts | 1✔️ | 503s | ||
test/parallel/xyk-pallet.API.pool.soloToken.test.ts | 7✔️ | 1295s | ||
test/parallel/xyk-pallet.API.pool.weightedPools.test.ts | 6✔️ | 1859s | ||
test/parallel/xyk-pallet.API.poolLiqidity.claimReward.test.ts | 3✔️ | 1019s | ||
test/parallel/xyk-pallet.API.poolLiqidity.mintLiqudity.test.ts | 3✔️ | 419s | ||
test/parallel/xyk-pallet.API.validateStatus.test.ts | 3✔️ | 779s |
✔️ test/parallel/xyk-pallet.API.accuracy.shared.pool.test.ts
Accuracy > Shared pool
✔️ Each user who minted owns the same % of tokens - one user gets extra token
✔️ Each user who minted onws the same % of tokens - two users gets the extra
✔️ Each user who minted onws the same % of tokens - divisible by 3
✔️ Each user who minted different % of tokens [50k,25k,5k]- get diff amounts
✔️ Given 3 users that minted liquidity WHEN only one activated the rewards THEN all rewards belongs to him on this pool
✔️ test/parallel/xyk-pallet.API.parachainStacking.activateRewards.test.ts
✔️ Given a user with bonded but not activated liq tokens WHEN he tries to activate THEN the tokens are activated for rewards
✔️ test/parallel/xyk-pallet.API.pool.deactivated.test.ts
✔️ GIVEN a disabled pool the user can still interact with it: Burn, deactivate Liq
✔️ GIVEN a disabled solo rewarded token the user can still interact with it: deactivate Liq & claim rewards
✔️ test/parallel/xyk-pallet.API.pool.promoting.test.ts
✔️ GIVEN a promoted pool WHEN more pools gets activated THEN shares are decreased and equally divided among all the activated pools
✔️ test/parallel/xyk-pallet.API.pool.soloToken.test.ts
✔️ GIVEN pool and solo token AND both were created at the same time AND the activated amounts are similar THEN the available rewards are the same AND when the user claims, it gets the same amounts
✔️ GIVEN pool and solo token AND both were created at the same time AND the activated amounts are similar AND then some new activation happens after one session and some deactivation THEN the poolRewards storage is the same
✔️ GIVEN a solo token rewards setup, WHEN weight goes from 20 to 0 THEN no more rewards will be granted for new users or new activations
✔️ GIVEN a solo token rewards setup WHEN the user activates or deactivates THEN MPL is also modified
✔️ GIVEN a solo token rewards setup WHEN a user activates the token, then it gets reserved
✔️ GIVEN a solo token rewards setup WHEN a user deactivates all the tokens, then they are free again
✔️ GIVEN a solo token rewards setup WHEN a user deactivates all the tokens THEN he can claim some available rewards
✔️ test/parallel/xyk-pallet.API.pool.weightedPools.test.ts
✔️ Check that we can get the list of promoted pools with proofOfStake.promotedPoolRewards data storage
✔️ Validate that weight can be modified by using updatePoolPromotion AND only sudo can update weights
✔️ Testing that the sum of the weights can be greater than 100
✔️ GIVEN a pool WHEN it has configured with 0 THEN no new issuance will be reserved
✔️ GIVEN a deactivated pool WHEN its configured with more weight, THEN rewards are now active, new users can get portion of those rewards AND issuance grows
✔️ GIVEN an activated pool WHEN pool was deactivated THEN check that the user will still get some rewards from the curve, and storage is updated
✔️ test/parallel/xyk-pallet.API.poolLiqidity.claimReward.test.ts
✔️ Check that rewards are generated and can be claimed on each session, then burn all tokens and rewards wont be available
✔️ Given a pool with 2 users with activated rewards WHEN more than one period last AND the user burn all liquidity THEN pool is destroyed but users can still claim pending rewards
✔️ Given a pool with user with activated rewards WHEN it was deactivated AND activated again THEN the user can receive a reward in both a deactivated and activated pool
✔️ test/parallel/xyk-pallet.API.poolLiqidity.mintLiqudity.test.ts
✔️ Check that a user that mints on a promoted pool liquidity tokens are reserved
✔️ Check that a user that mints on a non-promoted pool liquidity tokens are free
✔️ Given 3 pool: token1-MGX, token2-MGX and token1-token2 WHEN token1-token2 is promoted THEN user can receive rewards from token1-token2 pool
✔️ test/parallel/xyk-pallet.API.validateStatus.test.ts
Validate initial status
✔️ User just minted on a promoted pool
✔️ User just minted and rewards generated
✔️ User just minted on a promoted pool and after rewards being generated mint some more
Loading