test: add fuzzing suite for i128 amount decoding to ensure BigInt pre…#96
Open
githoboman wants to merge 1 commit into
Open
Conversation
…cision consistency
|
@githoboman Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
SDK invariant test — directly calls scValToNative on 9 sentinel values (including I128_MAX, I128_MIN, and values just outside JS safe-integer range) and asserts typeof native === "bigint". If a future SDK version regresses to returning number, this fails immediately.
Closes #78
10k precision fuzz — generates i128 BigInts across the full signed range using a weighted fc.oneof: 2× weight on > Number.MAX_SAFE_INTEGER and < -Number.MAX_SAFE_INTEGER (the dangerous band), plus 1× weight on the full range. For each input it asserts BigInt(result.amount) === original — so any number-path fallback in the decoder would fail the moment a value exceeds ±2⁵³−1.