Skip to content

[GASP-1099] Prometheus metrics for gasp-node (#421) #356

[GASP-1099] Prometheus metrics for gasp-node (#421)

[GASP-1099] Prometheus metrics for gasp-node (#421) #356

GitHub Actions / E2E report yarn test-sequential-autocompound succeeded Jan 27, 2025 in 0s

6 passed, 0 failed and 1 skipped

Tests passed successfully

✅ e2eTests/reports/junit.xml-58023b60-dcb4-11ef-bb4d-f13393683d50.xml

7 tests were completed in 228s with 6 passed, 0 failed and 1 skipped.

Test suite Passed Failed Skipped Time
test/sequential/rewardsv2.poolLiquidityRewards.test.ts 4✅ 156s
test/story/rewardsStory.test.ts 2✅ 1⚪ 72s

✅ test/sequential/rewardsv2.poolLiquidityRewards.test.ts

rewards v2 tests › Error cases
  ✅ Given a user with Liquidity on non promoted pool When tries to activate Then extrinsic fail
rewards v2 tests › A user can get rewards
  ✅ Given a user with Liquidity activated When tries to deactivate Then the user gets all tokens burn and rewards amount are readable in RPC THEN the user can claim them
  ✅ Given a user with Liquidity activated When tries to burn some Then the user gets automatically deactivated that amount And rewards are stored in NotYetClaimed section in rewards info
  ✅ Given a user with Liquidity activated When tries to mint some more Then the user activated amount will grow on that value

✅ test/story/rewardsStory.test.ts

Story tests > Rewards - autocompound
  ✅ Given a user1 with minted tokens when two sessions happen, then there are available rewards
  ✅ Given a user2 WHEN available rewards can claim and mgas are increased
  ⚪ Given a user3 WHEN available rewards can autocompund