test(ripple): assert displayed address response (7143) - #79
Draft
BitHighlander wants to merge 1 commit into
Draft
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The screenshot-selected Ripple address test now asserts the returned known address on 7.14.3 and later, catching shared-response corruption during debug capture. Earlier versions keep their existing display execution.
All three address tests pass with screenshot capture against the full 7.14.3 emulator at 1ce4d3961. The assertion reproduces an empty address on the unfixed predecessor. Forced UDP and isolated emulator storage; no hardware used.
Bounded older-release audit unit. Firmware pin integration remains pending. No upstream merge or Copilot request.