[MGX-632] 3rdparty rewards #1169
GitHub Actions / E2E report yarn test-governance
succeeded
Oct 2, 2023 in 1s
E2E report yarn test-governance ✔️
✔️ e2eTests/reports/junit-10176ad0-6142-11ee-81de-b37b7f3348ae.xml
21 tests were completed in 2418s with 21 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| test/parallel/council-pallet.API.fundation.test.ts | 21✔️ | 2418s |
✔️ 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