-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
feat: enable coverage linter for functional tests #6479
Conversation
|
f56e7cb
to
e0c580e
Compare
This pull request has conflicts, please rebase. |
…oteraw We indeed doesn't have functional tests for them yet, but this linter will help to avoid adding new RPCs without tests
e0c580e
to
2e509b9
Compare
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, utACK 2e509b9
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.
utACK 2e509b9
nit, please be more careful with commit naming in future. Commits should probably be
|
Issue being fixed or feature implemented
https://github.com/dashpay/dash-issues/issues/63
What was done?
Add functional tests for
getblockheaders
Hide RPC
cleardiscouraged
(as it is used only for functional tests) and RPCgetpoolinfo
(deprecated long time ago)Add a workaround to ignore these RPCs
getmerkleblocks
,voteraw
,debug
,coinjoinsalt
at the momentEnables linter for coverage
How Has This Been Tested?
Run locally with
test/functional/test_runner.py -j20 --previous-releases --coverage --extended
Enabled in CI
Breaking Changes
N/A if hidding
cleardiscouraged
is not a breaking change.Checklist: