Add unit test for Helper.SHA256(String) #1071
No reviewers
Labels
No labels
android: closed alpha
android: open beta
app-parity
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
creator
Epic
good first issue
hacktoberfest
help wanted
icebox
Invalid
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
product review
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-android#1071
Loading…
Reference in a new issue
No description provided.
Delete branch "sha256-unittest"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
PR Checklist
Please check all that apply to this PR using "x":
PR Type
What kind of change does this PR introduce?
Fixes
Issue Number:
What is the current behavior?
No way to ensure changes in SHA256 method result in the same output.
What is the new behavior?
Running this unit test after performing any modification to SHA256 method will allow developers and reviewers detect if the code change still returns the same result.
Other information
This PR should be merged before https://github.com/lbryio/lbry-android/pull/1067 to ensure the output is still the same. Reviewer will be able then to see test works before merging PR 1067 so it could verify changes in that PR return the same hash.
Looks good. Thanks.