-
Notifications
You must be signed in to change notification settings - Fork 1
test(wallet-service): harden /version contract #428
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
tuliomir
wants to merge
5
commits into
master
Choose a base branch
from
chore/pr-420-hardening
base: master
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.
+103
−2
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
df1493e
test(wallet-service): harden /version contract
tuliomir d9f1823
test(wallet-service): centralize /version test fixture
tuliomir 3d3abd7
Merge branch 'master' into chore/pr-420-hardening
tuliomir a6f62c2
test(wallet-service): group version() tests and cover legacy payload
tuliomir 3281c44
test(wallet-service): restore mocks after each version() test
tuliomir 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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,45 @@ | ||
| import { FullnodeVersionSchema } from '@src/schemas'; | ||
| import { defaultTestVersionData } from '@tests/utils'; | ||
|
|
||
| // Regression guard for the testnet outage that motivated PR 420: the | ||
| // fullnode added `native_token.version` and the lambda crashed because the | ||
| // nested object did not allow it. Locking the modern payload in as a | ||
| // passing case prevents that fix from being reverted by accident. | ||
| test('FullnodeVersionSchema regression: native_token.version is accepted', () => { | ||
| const payload = { | ||
| ...defaultTestVersionData(), | ||
| native_token: { name: 'Hathor', symbol: 'HTR', version: 0 }, | ||
| }; | ||
| const { error, value } = FullnodeVersionSchema.validate(payload); | ||
| expect(error).toBeUndefined(); | ||
| expect(value.native_token).toEqual({ name: 'Hathor', symbol: 'HTR', version: 0 }); | ||
| }); | ||
|
|
||
| test('FullnodeVersionSchema accepts a legacy fullnode payload without native_token.version', () => { | ||
| // defaultTestVersionData() returns a payload whose native_token has no `version`. | ||
| const { error } = FullnodeVersionSchema.validate(defaultTestVersionData()); | ||
| expect(error).toBeUndefined(); | ||
| }); | ||
|
|
||
| // Design-intent guard: native_token is intentionally strict — any unknown | ||
| // field there fails validation so a contract test (and not a production | ||
| // outage) surfaces fullnode schema drift. | ||
| test('FullnodeVersionSchema rejects unknown fields under native_token', () => { | ||
| const payload = { | ||
| ...defaultTestVersionData(), | ||
| native_token: { name: 'Hathor', symbol: 'HTR', version: 0, icon: 'data:image/png;base64,...' }, | ||
| }; | ||
| const { error } = FullnodeVersionSchema.validate(payload); | ||
| expect(error).toBeDefined(); | ||
| expect(error!.message).toMatch(/native_token\.icon/); | ||
| }); | ||
|
|
||
| test('FullnodeVersionSchema rejects a non-integer native_token.version', () => { | ||
| const payload = { | ||
| ...defaultTestVersionData(), | ||
| native_token: { name: 'Hathor', symbol: 'HTR', version: 1.5 }, | ||
| }; | ||
| const { error } = FullnodeVersionSchema.validate(payload); | ||
| expect(error).toBeDefined(); | ||
| expect(error!.message).toMatch(/native_token\.version/); | ||
| }); | ||
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.
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.
We should not reference the PR solving the outage if possible, the comment should document the core issue this addresses instead.
I think a link to an issue describing the problem would be good if the core issue was too complex to describe in the comment.