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 fuzz tests for hollow account completion #4855
Add fuzz tests for hollow account completion #4855
Conversation
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.
Some ideas:
- a very short expiration time
- throw in some deletions
- having a small enough inventory of keys so we end-up reusing the keys for the operations
- in the future (maybe not this PR), having accounts finalized not from the payer signature only (when we update the implementation for this)
Signed-off-by: Stoyan Stoyanov <stoyan.stoyanov@limechain.tech>
Signed-off-by: Stoyan Stoyanov <stoyan.stoyanov@limechain.tech>
Signed-off-by: Stoyan Stoyanov <stoyan.stoyanov@limechain.tech>
Signed-off-by: Stoyan Stoyanov <stoyan.stoyanov@limechain.tech>
Signed-off-by: Stoyan Stoyanov <stoyan.stoyanov@limechain.tech>
Signed-off-by: Stoyan Stoyanov <stoyan.stoyanov@limechain.tech>
cbac879
to
43d3e2a
Compare
Signed-off-by: Stoyan Stoyanov <stoyan.stoyanov@limechain.tech>
…t-completion-transactions
Signed-off-by: Stoyan Stoyanov <stoyan.stoyanov@limechain.tech>
Signed-off-by: Stoyan Stoyanov <stoyan.stoyanov@limechain.tech>
Signed-off-by: Stoyan Stoyanov <stoyan.stoyanov@limechain.tech>
…t-completion-transactions
…t-completion-transactions
…t-completion-transactions
…t-completion-transactions
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #4855 +/- ##
==============================================
+ Coverage 0 91.09% +91.09%
- Complexity 0 16898 +16898
==============================================
Files 0 1279 +1279
Lines 0 48476 +48476
Branches 0 4890 +4890
==============================================
+ Hits 0 44159 +44159
- Misses 0 3390 +3390
- Partials 0 927 +927 ☔ View full report in Codecov by Sentry. |
…t-completion-transactions
Signed-off-by: Miroslav Gatsanoga <miroslav.gatsanoga@limechain.tech>
Signed-off-by: Miroslav Gatsanoga <miroslav.gatsanoga@limechain.tech>
Signed-off-by: Miroslav Gatsanoga <miroslav.gatsanoga@limechain.tech>
Signed-off-by: Miroslav Gatsanoga <miroslav.gatsanoga@limechain.tech>
Signed-off-by: Miroslav Gatsanoga <miroslav.gatsanoga@limechain.tech>
Signed-off-by: Miroslav Gatsanoga <miroslav.gatsanoga@limechain.tech>
Signed-off-by: Miroslav Gatsanoga <miroslav.gatsanoga@limechain.tech>
Signed-off-by: Miroslav Gatsanoga <miroslav.gatsanoga@limechain.tech>
Signed-off-by: Miroslav Gatsanoga <miroslav.gatsanoga@limechain.tech>
...java/com/hedera/services/bdd/spec/infrastructure/providers/ops/BiasedDelegatingProvider.java
Show resolved
Hide resolved
...va/com/hedera/services/bdd/spec/infrastructure/providers/ops/hollow/RandomHollowAccount.java
Outdated
Show resolved
Hide resolved
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.
Two minor comments, overall looks great to me!
Signed-off-by: Miroslav Gatsanoga <miroslav.gatsanoga@limechain.tech>
Signed-off-by: Miroslav Gatsanoga <miroslav.gatsanoga@limechain.tech>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Thanks @tinker-michaelj, pushed some updates regarding the comments. |
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, nice work!
Signed-off-by: Stoyan Stoyanov stoyan.stoyanov@limechain.tech
Description:
Testing of hollow account completion by fuzzing different operations.
The test randomly runs the following operations (with bias defined in properties file):
Note: When creating an account it is saved in both the key and account registry and to differentiate between SECP256K1 keys and account keys, but still easily get one from the other we create hollow account names by adding "#" to the key name that created it.
Related issue(s):
Fixes #4633