Skip to content
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

test(types/address): add additional unit tests for address.LengthPrefix and a… #19964

Merged

Conversation

EmilGeorgiev
Copy link
Contributor

@EmilGeorgiev EmilGeorgiev commented Apr 5, 2024

…ddress.MustLengthPrefix

Description

Improve test coverage as added a new unit tests for the functions address.LengthPrefix and address.MustLengthPrefix

Closes: according to the CONTRIBUTING.md guidlines, issue is not needed for very small or blatantly obvious problems.


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • [ x] included the correct type prefix in the PR title
  • [ x] confirmed ! in the type prefix if API or client breaking change
  • [ x] targeted the correct branch (see PR Targeting)
  • [ x] provided a link to the relevant issue or specification
  • [ x] reviewed "Files changed" and left comments if necessary
  • [ x] included the necessary unit and integration tests
  • [ x] added a changelog entry to CHANGELOG.md
  • [ x] updated the relevant documentation or specification, including comments for documenting Go code
  • [ x] confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • Tests
    • Added tests for handling 0-byte addresses and testing panic behavior for overly long addresses.

@EmilGeorgiev EmilGeorgiev requested a review from a team as a code owner April 5, 2024 04:23
Copy link
Contributor

coderabbitai bot commented Apr 5, 2024

Walkthrough

Walkthrough

The recent update aims to bolster the testing suite for address handling, particularly focusing on addressing edge cases. It includes a new test to validate 0-byte address handling and introduces a test to ensure correct panic behavior for excessively long addresses. These changes aim to improve the reliability and robustness of address processing by addressing potential scenarios that might result in unexpected outcomes.

Changes

File Change Summary
types/address/store_key_test.go - Added test for 0-byte address handling in TestLengthPrefix
- Introduced TestMustLengthPrefix to test panic with long addresses

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@EmilGeorgiev EmilGeorgiev changed the title test(types): add additional unit tests for address.LengthPrefix and a… test(address): add additional unit tests for address.LengthPrefix and a… Apr 5, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Review Status

Configuration used: .coderabbit.yml

Commits Files that changed from the base of the PR and between 558c950 and 19a952f.
Files selected for processing (1)
  • types/address/store_key_test.go (4 hunks)
Additional Context Used
Path-based Instructions (1)
types/address/store_key_test.go (2)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.


Pattern **/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"

Additional comments not posted (1)
types/address/store_key_test.go (1)

17-23: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [20-31]

LGTM! The addition of a test case for a 0-byte address in TestLengthPrefix is a good practice for edge case testing.

Comment on lines 48 to 77
func (suite *StoreKeySuite) TestMustLengthPrefix() {
require := suite.Require()
addr10byte := []byte{0, 1, 2, 3, 4, 5, 6, 7, 8, 9}
addr256byte := make([]byte, 256)

tests := []struct {
name string
addr []byte
expStoreKey []byte
expPanic bool
}{
{"add length prefix for address", addr10byte, append([]byte{byte(10)}, addr10byte...), false},
{"too long address must rise a panic", addr256byte, nil, true},
}

for _, tt := range tests {
suite.Run(tt.name, func() {
defer func() {
r := recover()
if tt.expPanic {
require.NotNil(r)
} else {
require.Nil(r)
}
}()
storeKey := address.MustLengthPrefix(tt.addr)
require.Equal(tt.expStoreKey, storeKey)
})
}
}
Copy link
Contributor

@coderabbitai coderabbitai bot Apr 5, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider refining the test case descriptions in TestMustLengthPrefix for clarity and accuracy. For example, "add length prefix for address" could be more descriptive about the expected outcome, and "too long address must rise a panic" could be corrected to "too long address must raise a panic".

-		{"add length prefix for address", addr10byte, append([]byte{byte(10)}, addr10byte...), false},
-		{"too long address must rise a panic", addr256byte, nil, true},
+		{"10-byte address with length prefix", addr10byte, append([]byte{byte(10)}, addr10byte...), false},
+		{"256-byte address triggers panic due to excessive length", addr256byte, nil, true},

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
func (suite *StoreKeySuite) TestMustLengthPrefix() {
require := suite.Require()
addr10byte := []byte{0, 1, 2, 3, 4, 5, 6, 7, 8, 9}
addr256byte := make([]byte, 256)
tests := []struct {
name string
addr []byte
expStoreKey []byte
expPanic bool
}{
{"add length prefix for address", addr10byte, append([]byte{byte(10)}, addr10byte...), false},
{"too long address must rise a panic", addr256byte, nil, true},
}
for _, tt := range tests {
suite.Run(tt.name, func() {
defer func() {
r := recover()
if tt.expPanic {
require.NotNil(r)
} else {
require.Nil(r)
}
}()
storeKey := address.MustLengthPrefix(tt.addr)
require.Equal(tt.expStoreKey, storeKey)
})
}
}
func (suite *StoreKeySuite) TestMustLengthPrefix() {
require := suite.Require()
addr10byte := []byte{0, 1, 2, 3, 4, 5, 6, 7, 8, 9}
addr256byte := make([]byte, 256)
tests := []struct {
name string
addr []byte
expStoreKey []byte
expPanic bool
}{
{"10-byte address with length prefix", addr10byte, append([]byte{byte(10)}, addr10byte...), false},
{"256-byte address triggers panic due to excessive length", addr256byte, nil, true},
}
for _, tt := range tests {
suite.Run(tt.name, func() {
defer func() {
r := recover()
if tt.expPanic {
require.NotNil(r)
} else {
require.Nil(r)
}
}()
storeKey := address.MustLengthPrefix(tt.addr)
require.Equal(tt.expStoreKey, storeKey)
})
}
}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@EmilGeorgiev, thank you for making the requested changes. It's great to see the test case descriptions improved for clarity and accuracy. Keep up the good work! 🚀


If you found this review helpful, would you consider giving us a shout-out on X?
Thank you for using CodeRabbit!

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review Status

Configuration used: .coderabbit.yml

Commits Files that changed from the base of the PR and between 19a952f and 20ad83f.
Files selected for processing (1)
  • types/address/store_key_test.go (4 hunks)
Files skipped from review as they are similar to previous changes (1)
  • types/address/store_key_test.go

@@ -3,9 +3,8 @@ package address_test
import (
"testing"

"github.com/stretchr/testify/suite"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make lint-fix

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@julienrbrt julienrbrt changed the title test(address): add additional unit tests for address.LengthPrefix and a… test(types/address): add additional unit tests for address.LengthPrefix and a… Apr 5, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review Status

Configuration used: .coderabbit.yml

Commits Files that changed from the base of the PR and between 20ad83f and b135c2a.
Files selected for processing (1)
  • types/address/store_key_test.go (3 hunks)
Files skipped from review as they are similar to previous changes (1)
  • types/address/store_key_test.go

@tac0turtle tac0turtle added this pull request to the merge queue Apr 5, 2024
Merged via the queue into cosmos:main with commit dcec6ad Apr 5, 2024
55 of 58 checks passed
alpe added a commit to alpe/cosmos-sdk that referenced this pull request Apr 8, 2024
* main: (45 commits)
  build(deps): Bump github.com/decred/dcrd/dcrec/secp256k1/v4 from 4.2.0 to 4.3.0 (cosmos#19913)
  build(deps): Bump google.golang.org/grpc from 1.62.1 to 1.63.0 (cosmos#19929)
  test(types/address): add additional unit tests for address.LengthPrefix and a… (cosmos#19964)
  refactor(x/bank)!: remove Address.String() (cosmos#19954)
  build(deps): Bump github.com/prometheus/common from 0.51.1 to 0.52.2 (cosmos#19930)
  fix(x/epochs): Fix init genesis (cosmos#19958)
  feat(core,runtime): transaction service (exec mode) (cosmos#19953)
  fix(x/authz): non utf-8 characters in logs (cosmos#19923)
  build(deps): Bump golang.org/x/crypto from 0.21.0 to 0.22.0 (cosmos#19960)
  chore: fix spelling errors (cosmos#19957)
  fix(x/tx): don't shadow Amino marshalling error messages (cosmos#19955)
  refactor(types): loosen module.AppModule interface (cosmos#19951)
  feat(core): add `TxValidator` interface (cosmos#19950)
  build(deps): Bump cosmossdk.io/store from 1.0.2 to 1.1.0 in /x/epochs (cosmos#19947)
  feat(x/epochs): upstream osmosis epoch module (cosmos#19697)
  build(deps): Bump bufbuild/buf-setup-action from 1.30.0 to 1.30.1 (cosmos#19928)
  refactor(x/genutil)!: remove Address.String() (cosmos#19926)
  docs(x/mint): Fix inconsistency in mint docs  (cosmos#19915)
  build(deps): Bump github.com/regen-network/gocuke from 1.1.0 to 1.1.1 in /orm (cosmos#19920)
  feat: Integrate grpc configuration into client.toml (cosmos#19905)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants