-
Notifications
You must be signed in to change notification settings - Fork 6
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
R/test utils #70
Merged
Merged
R/test utils #70
Changes from all commits
Commits
Show all changes
60 commits
Select commit
Hold shift + click to select a range
21760a8
Move active fps calca to finality mod
7892932
Fix: Non-zero fp voting power check
ab5e5ea
Move FP_SET to finality state where it belongs
12f826d
Split staking and finality execution handlers
5ee7987
Move finality stuff out of btc-staking and into babylon-finality
c56df77
Add babylon-finality contract (WIP)
806409e
Fix rebase errors
44f1919
Remove sudo handlers from the staking contract
3177ada
Add staking slash handler / msg
065e1ef
Refactor: use staking queries, and batched active FPs processing
b09b542
cargo fmt
262b4a4
Add babylon contract version to store in passing
63cdd1f
Add finality contract instantiation
4b6bd78
Remove finality dependendency
feed346
Rename to btc-finality for consistency
246ea4b
Refactor: route slashing through babylon only
a145f7e
Fix: proper routing / auth of slashing message
7d4c030
Update / Set staking address during finality contract instantiation
16e94f5
Fix / adapt benches
066ea79
Improve / adjust size checks
49b6ec8
Fix / adjust staking tests
3562f8b
Remove unused structs
95ff295
Make test helpers public
4e43626
Update schema
0938d3b
Fix: tests compilation / imports
00efde3
Ignore broken (no multi-test) tests
d3aece7
Fix / unify schema bin names
6124b93
Update btc-finality schemas
9af350c
Add btc-finality to CI releases
a7a03ad
Add btc-finality integration tests
21a72d9
Add btc finality to init tests
4646f1e
Add multitest to btc-finality
7a4c1e9
Add convenience contracts fields to suite
2f6583e
Remove unused funds
dfc0589
Add public randomness commitment mt
c6935e0
Fix: FP smart query results processing
8d7f357
Remove original test
6c34f64
Add TODO
14cdb0d
Move sudo msg from staking to finality
3380a9d
Add new at height app ctor
1f9f05c
Add finality sig happy path mt
af7c705
Add test modules for clarity
5c339e3
Add finality round works mt
bca20d1
Add slashing works mt
543e639
Remove original finality (no mt) tests
4bdc93a
Fix: slashing test
5380765
Feature gate / disable IBC messages for (multi-)tests
8b1ccf5
Fix: Avoid full-validation failure / bug in CI
be727ae
Remove (unused) denom from config
e0af2d9
Remove (unused / redundant) params from staking params
05438bb
Update schema
29a1b16
Move staking test helpers to the test-utils package
d67f7d8
Move finality test helpers to the test-utils package
01f98cc
Improve Params setting / passing
6434ca8
Enable / add full validation feature for finality
84a63b1
Add test_utils pub mod
91a2c36
Fix: tests under full validation
16a8a4c
Enable full validation tests for all contracts
365d5c4
Full validation also for babylon contract
5f42c3b
Merge branch 'main' into r/test-utils
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
Does the finality contract need the option for full validation? I thought the full validation is only relevant for Babylon <-> contract interaction, and only BTC staking contracts needs to have that. In theory finality contract can work with BTC staking contract with or without full validation.
For testing finality contract, we can always use BTC staking contract without full validation imo
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.
Yes, but this is a stronger setting, in which we confirm the
full-validation
feature works also in / for the multi-contract tests.In fact all this comes from the fact that CI was running workspace tests with the full validation feature enabled, and they were failing for the finality contract.
I've now enabled that back, and tests are passing.
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 see. Is there a way to make this feature only for developments/tests? np with me if we cannot do it though
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.
It's already like that. Because the code under the
library
feature, used when importing other contracts, is only used / invoked from test code. These high levelfull-validation
features in contracts other than the staking contract are just wrappers to the staking one; so that the feature can be enabled on purpose. Which, only affects tests.