| No | Scenario | Pre-condition | Pre-condition check | Expected result | Expected result check | Covered By |
|---|---|---|---|---|---|---|
| 1 | Sequencer successful state update writes |
|
🛑 (missing) |
State update written is with correct data (i.e height, da height, da layer configured by the rollapp) | 🛑 (missing) |
TODO |
| 2 | Sequencer failure to write to settlement layer is recovered | At least 2 rollapps registered, Rollapp A and Rollap B. Sequencer is the proposer of Rollapp A. | - [ ] Check rollapp registration and sequencer roles. - [ ] Take down the settlement layer. - [ ] Monitor rollapp health status. |
While rollapp is unhealthy: - Block production stops. - Sending transactions fails. After recovery: - Block production resumes. - Transactions pass. - State updates are written to the settlement layer. |
- [ ] Verify block production and transaction status during downtime and after recovery. - [ ] Confirm state update in settlement layer post-recovery. |
TODO |
| 3 | Sequencer failure to write to Celestia DA layer is recovered | At least 2 rollapps registered, Rollapp A and Rollap B. Sequencer is the proposer of Rollapp A. | - [ ] Ensure Celestia DA layer is accessible. - [ ] Take down the DA layer. - [ ] Keep the rollapp running. - [ ] Monitor rollapp health status. |
While rollapp is unhealthy: - Block production stops. - Sending transactions fails. After recovery: - Block production resumes. - Transactions pass. - State updates are written to the Celestia DA layer. |
- [ ] Check for block production cessation and transaction failures when DA layer is down. - [ ] Confirm block production, transactions, and state updates post-recovery. |
TODO |