Staging env configuration update #2203
GitHub Actions / E2E report yarn test-rolldownWithdrawal
succeeded
Jan 30, 2025 in 0s
11 passed, 0 failed and 0 skipped
✅ e2eTests/reports/junit.xml-2c45e410-dea6-11ef-8d9e-8fde1a23b2ae.xml
11 tests were completed in 1080s with 11 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| test/sequential/rolldown.withdraw.fees.test.ts | 5✅ | 118s | ||
| test/sequential/rolldown.withdraw.merkleRoot.test.ts | 6✅ | 962s |
✅ test/sequential/rolldown.withdraw.fees.test.ts
✅ GIVEN a withdrawal, WHEN paying with GASP and withdrawing GASP, some fees goes to treasury
✅ GIVEN a withdrawal, WHEN paying with GASP and withdrawing Eth, some fees goes to treasury
✅ GIVEN a withdrawal, WHEN paying with GASP and withdrawing ALL GASP, extrinsic fail
✅ GIVEN a withdrawal, WHEN user having only Eth and withdrawing Eth, extrinsic fail
✅ Given a fee withdrawal payment WHEN withdrawal is sent from another account THEN the fee is deducted from from sender's account
✅ test/sequential/rolldown.withdraw.merkleRoot.test.ts
Withdraw & Batches tests -
✅ Given a cancel WHEN block is processed THEN it will create an update that needs to be sent through a batch to L1 for justification
✅ Given a withdraw extrinsic run WHEN token address does not exist THEN a withdraw fail and no l2update is stored
✅ Given a withdraw extrinsic run WHEN token address exist but requester does not have funds THEN a withdraw fail and no l2update is stored
✅ Given a succeed withdraw, when block is executed Then tokens are removed from user wallet
✅ GIVEN <batchSize - 1> withdraws, AND manually generated batch and create another withdraw for some other network (arb) THEN the batch is not generated
✅ Given a failed deposit TX, then a withdrawal can be created by `refundFailedDeposit
Loading