This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add tests for Polkadot runtime weights and fees #1090
Add tests for Polkadot runtime weights and fees #1090
Changes from 10 commits
993d83c
13168bf
7ec2704
af7ce8e
889d883
5db64b5
e0906fe
74136ea
ee802a7
9443cc5
5081068
38b27a6
68a563c
3d00567
245ad73
c92b4bf
e602134
e15d06f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
a lot of these values will be changing coming up i.e. staking
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.
Yeah, which forces me to ask: what type of breakage is this preventing?
sanity_checks_...
even though the chance of breaking them is low.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.
I disagree. Changes in one Pallet don't necessarily affect another Pallet. Tests can and should evolve over time, and I don't think these tests are particularly challenging to maintain.
I think the advantage of having these tests is that it makes sure that people realize a change happened in Substrate (by seeing a companion PR to update the tests) instead of silently having weights changed from under them.
In an extreme example, I guess we'd want to prevent something like EIP 1884, which changed the pricing of certain OPCODEs and thus some security assumptions.
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.
Makes sense.