Feature/stable pool mgx 1307 #727
GitHub Actions / E2E report yarn test-rolldownPreOperationWithdrawal
succeeded
Nov 25, 2024 in 1s
E2E report yarn test-rolldownPreOperationWithdrawal ✅
✅ e2eTests/reports/junit.xml-5ddcbbe0-ab82-11ef-8b60-370c98d3421c.xml
18 tests were completed in 2298s with 18 passed, 0 failed and 0 skipped.
Test suite | Passed | Failed | Skipped | Time |
---|---|---|---|---|
test/sequential/rolldown.withdraw.preOperation.test.ts | 18✅ | 2298s |
✅ test/sequential/rolldown.withdraw.preOperation.test.ts
Pre-operation withdrawal tests -
✅ Given <batchSize> withdrawals WHEN they run successfully THEN a batch is generated AUTOMATICALLY from that L1, from ranges of (n,n+<batchSize>-1)
✅ Given a withdraw extrinsic run WHEN tokens are available THEN a withdraw will happen and l2Requests will be stored waiting for batch
✅ Given a withdraw extrinsic run WHEN token is Eth and user has some tokens THEN a withdraw will happen and update will be stored on l2Requests and will be stored waiting for batch
✅ Given a withdraw in a batch extrinsic, When one of the calls fail from the batch, then tokens are reverted ( transactional )
✅ Given <3> withdrawals WHEN they run successfully and we wait <batchPeriod> blocks, a batch is created upon reaching the period
✅ Given <1> withdrawal WHEN we manually generate a batch for it THEN a batch is generated
✅ GIVEN <batchSize - 1> withdraws and create manualBatch And wait for a timed generation WHEN another withdrawal is submitted THEN a batch is generated
✅ GIVEN <batchSize - 1> withdraws and create manualBatch And wait for a timed generation WHEN create batch with <batchSize - 1> withdrawal and add another one THEN a batch is generated automatically
✅ GIVEN a manually generated batch, from A,B, WHEN timed happen THEN automatic batch will skip those manual ids
✅ GIVEN a manually generated batch, from A,B, WHEN up to 32 withdrawals happen THEN another automatic batch will run only including that missing id
✅ GIven a utility.batch ( batched tx of 35 and last item in the utility.batch is the mm_on ) When maintenance mode, THEN No automatic batch can happen
✅ Creating two merkle trees generates the same output
✅ Given a manually batch generation, WHEN is not the forced, THEN start-end will be calculated automatically
✅ Given a manually batch generation, WHEN is the forced ( sudo ) , THEN start-end must be set manually
✅ Given a non-forced manually generation, WHEN triggered, start will be the latest index from the last generated MAX( manual or automatically ) and last will be the latest requestId
✅ GIVEN a manual batch WHEN no pending requests THEN no batch is generated BUT tokens are subtracted
✅ GIVEN manual batch THEN requires as parameter of the Eth Chain
✅ GIVEN manual batch THEN requires as parameter of the Arb Chain
Loading