-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add governance e2e tests #115
Add governance e2e tests #115
Conversation
Each voter's tally and locked funds (for the track of the test's referendum, which is `SmallTipper`), are checked at 2 other important stages: 1. after the referendum's cancellation, since this event shouldn't affect either 2. after the explicit removal of such votes from the now cancelled referendum, which should alter these data accordingly.
Checking each of the test's 3 voting account's class locks and voting data was rewritten for simplicity.
735b230
to
bd9f25f
Compare
Voting events have been introduced in #4613 and #6544, but Polkadot/Kusama runtimes have not yet been updated to reflect this. Instead of storing ALL events for the transactions containing the voting extrinsics, only those for `convictionVoting` are stored i.e. they will be empty, which will trigger an error anyway when the runtimes are updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
there is an empty file packages/shared/src/xcm/sendXcmFromRelay ?
I was going to use it for some common code from the people chain tests and these, but decided against it. |
/bot merge |
|
Similar to #63, this PR adds E2E tests to governance functionality.
Right now, it tests a referendum's lifecycle.
This is still WIP.