Skip to content

fix update validation

Sign in for the full log view
GitHub Actions / E2E report yarn test-crowdloan succeeded Nov 27, 2024 in 0s

E2E report yarn test-crowdloan ✅

Tests passed successfully

✅ e2eTests/reports/junit.xml-c56621d0-acf3-11ef-b9fe-b5c9c6ac46ee.xml

12 tests were completed in 642s with 12 passed, 0 failed and 0 skipped.

Test suite Passed Failed Skipped Time
test/sequential/crowdloan.API.claiming.test.ts 6✅ 366s
test/sequential/crowdloan.API.test.ts 6✅ 276s

✅ test/sequential/crowdloan.API.claiming.test.ts

✅ Users receive different rewards when they confirm them before, during and after crowdloan
✅ A user can only change his reward-address with: crowdloan.updateRewardAddress AND user can claim some rewards if it provided some on the specified cl_id
Test that a user can claim when
  ✅ CL1 is fully setup and no other CL is setup
  ✅ CL1 is fully setup and CL2 setup the setCrowdloanAllocation
  ✅ CL1 is fully setup and CL2 setup the setCrowdloanAllocation and RewardVec
  ✅ CL1 is fully setup and CL2 setup the setCrowdloanAllocation and RewardVec and completeInitialization

✅ test/sequential/crowdloan.API.test.ts

Only sudo can
  ✅ crowdloan.setCrowdloanAllocation(crowdloanAllocationAmount)
  ✅ crowdloan.initializeCrowdloanRewardVec(rewards)
  ✅ crowdloan.completeCrowdloanInitialization(leaseEndingBlock)
✅ A reward needs to be fully setup with: setCrowdloanAllocation + initializeCrowdloanRewardVec + completeCrowdloanInitialization
✅ CL needs to be setup in order
✅ Total contributors returns the number of contributors per crowdloan AND validation of contributions is done when Initializing the cl rewards
View more details on GitHub Actions