Repository navigation
test: update guidance for agents for writing tests and follow-up fixes for lately added tests. #7859
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
Open
knst
wants to merge
6
commits into
dashpay:develop
Choose a base branch
from
knst:test-scenarios
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
test: update guidance for agents for writing tests and follow-up fixes for lately added tests. #7859
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
8a67e4d
test: RPC importelectrumwallet have functional tests, removed an exce…
knst 1435bef
test: follow-up for #7829: replace brand-new scenario to just extra c…
knst 4a19742
test: follow-up for #7821: check if wallet is locked after failed upg…
knst 8a620db
test: follow-up for #7838: replace brand new scenario to extra check
knst 0288ca9
docs: be more explicit about "scope", "scenario", "case" when writing…
knst 99cdb0b
test: follow-up for #7812: use less fixture to test quorum dkgstatus
knst 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
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
🟡 Suggestion: Verify passphrase changes retain mixing access
The signmessage failure proves that the mixing-only wallet was not elevated to full permissions, but a completely locked wallet produces the same error. The removed scenario also verified that coinjoin("start") succeeded after the passphrase change, so this consolidation loses the assertion that mixing access is preserved. The subsequent walletpassphrase call explicitly unlocks the wallet and hides that distinction. Restore the coinjoin("start") success assertion followed by coinjoin("stop") immediately after walletpassphrasechange in this existing scenario. Checking unlocked_until alone is insufficient: getwalletinfo returns nRelockTime, and CWallet::Lock() can clear the master key without clearing that timestamp.
source:
gemini-3.8-flash-high(phase1-reviewer: general);gpt-6.1-sol(phase2-reviewer: general, dash-core-commit-history)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.
Resolved (re-reviewed at
99cdb0b5): Your added successful CoinJoin start check proves that mixing access survives the passphrase change, while the existing signing rejection proves it is not escalated to full access. Stopping CoinJoin immediately afterward keeps the subsequent checks isolated.