[fix] batched txs handling (#665) #245
GitHub Actions / E2E report yarn test-seqgasless
succeeded
Dec 22, 2023 in 0s
E2E report yarn test-seqgasless ✅
✅ e2eTests/reports/junit.xml-3995bb70-a0ab-11ee-b0a8-d7078ce2011b.xml
7 tests were completed in 804s with 7 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| test/sequential/feeLock.API.config.test.ts | 4✅ | 432s | ||
| test/sequential/feeLock.API.feePayment.sequential.test.ts | 3✅ | 372s |
✅ test/sequential/feeLock.API.config.test.ts
✅ gasless- GIVEN a non sudo user WHEN feeLock configuration extrinsic is submitted THEN it fails with RequireSudo
✅ gasless- GIVEN an empty feeLock configuration (all options empty) WHEN sudo submit the extrinsic THEN Tx fails because insufficient params
✅ gasless- GIVEN a feeLock WHEN periodLength and feeLockAmount are set THEN extrinsic succeed and feeLock is correctly configured
✅ gasless- Changing feeLock config parameter on the fly is works robustly. Either automatic or manual unlocks the tokens
✅ test/sequential/feeLock.API.feePayment.sequential.test.ts
✅ gasless- GIVEN a feeLock configured (only Time and Amount ) WHEN the user swaps AND the user has not enough MGAs and has enough TURs THEN the extrinsic fails on submission
✅ gasless- GIVEN a feeLock configured (only Time and Amount ) WHEN the user swaps AND the user does not have enough MGAs THEN the extrinsic fails on submission
✅ gasless- Given a feeLock correctly configured (only Time and Amount ) WHEN the user swaps AND the user has enough MGAs THEN the extrinsic is correctly submitted
Loading