[fix] batched txs handling (#665) #245
GitHub Actions / E2E report yarn test-governance
succeeded
Dec 22, 2023 in 0s
E2E report yarn test-governance ✅
✅ e2eTests/reports/junit.xml-e9660ac0-a0a9-11ee-ba51-891657d4f76b.xml
21 tests were completed in 2760s with 21 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| test/parallel/council-pallet.API.fundation.test.ts | 21✅ | 2760s |
✅ test/parallel/council-pallet.API.fundation.test.ts
Council tests: Special rules for foundation addresses on mmON
✅ Test that Foundation address can/cannot close an already voted proposal
✅ Test that NoFoundation address can/cannot close an already voted proposal
✅ Test that NoCouncil address can/cannot close an already voted proposal
✅ Test that Foundation address can/cannot veto a proposal
✅ Test that NoFoundation address can/cannot veto a proposal
✅ Test that sudo address can veto a proposal
✅ Test that Foundation address can/cannot veto an already voted proposal
✅ Test that NoFoundation address can/cannot veto an already voted proposal
✅ Test that sudo address can veto an already voted proposal
✅ Test that sudo address cannot close an already voted proposal
Council tests: Special rules for foundation addresses on mmOFF
✅ Test that Foundation address can/cannot close an already voted proposal
✅ Test that NoFoundation address can/cannot close an already voted proposal
✅ Test that NoCouncil address can/cannot close an already voted proposal
✅ Test that Foundation address can/cannot veto a proposal
✅ Test that NoFoundation address can/cannot veto a proposal
✅ Test that sudo address can veto a proposal
✅ Test that Foundation address can/cannot veto an already voted proposal
✅ Test that NoFoundation address can/cannot veto an already voted proposal
✅ Test that sudo address can veto an already voted proposal
✅ Test that sudo address cannot close an already voted proposal
✅ Test that Closing a motion requires some time for Council mebers but not for founders
Loading