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(inflation): add supply checks #1827

Closed
wants to merge 1 commit into from
Closed

Conversation

Unique-Divine
Copy link
Member

@Unique-Divine Unique-Divine commented Mar 20, 2024

Summary by CodeRabbit

  • Refactor
    • Improved clarity and reusability of coin supply checks in the system.

Copy link
Contributor

coderabbitai bot commented Mar 20, 2024

Walkthrough

This update enhances code clarity and reusability related to burn coin supply checks within the inflation module. By moving these checks to separate functions, the changes facilitate better testing and maintenance. Additionally, the update aims to align with best practices by using bank total supply queries for validating state changes in MsgBurn, addressing specific objectives from linked issues.

Changes

Files Change Summary
x/inflation/keeper/keeper_test.go Extracted burn coin supply checks to separate functions.
x/inflation/keeper/msg_server_test.go Utilized separate functions for burn coin supply checks.

Assessment against linked issues

Objective Addressed Explanation
Use bank total supply queries to validate state changes in MsgBurn (#1825)

🐰✨
Changes afoot, in code we trust,
Clarity blooms, as functions adjust.
Burn the coins, but check them right,
In tests we trust, to code with might.
🌟🐇

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-tests 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 tests 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 tests.
    • @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.
  • The JSON schema for the configuration file is available here.
  • 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

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@Unique-Divine Unique-Divine marked this pull request as ready for review March 20, 2024 05:54
@Unique-Divine Unique-Divine requested a review from a team as a code owner March 20, 2024 05:54
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.

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between db4ee51 and 0314f21.
Files selected for processing (2)
  • x/inflation/keeper/keeper_test.go (1 hunks)
  • x/inflation/keeper/msg_server_test.go (1 hunks)
Additional comments: 1
x/inflation/keeper/msg_server_test.go (1)
  • 77-95: The addition of supply checks before and after the burn operation in the TestMsgBurn function is a solid improvement for validating the correctness of the burn functionality. This ensures that the test accurately reflects the expected behavior of the system when tokens are burned. The implementation correctly places the supply check outside of any conditional error handling, ensuring it's always executed. This is a good practice and aligns with the changes recommended for keeper_test.go.

Comment on lines +45 to +50
supplyBefore := nibiruApp.BankKeeper.GetSupply(ctx, "unibi")
err := nibiruApp.InflationKeeper.Burn(ctx, sdk.NewCoins(tc.burnCoin), tc.sender)
if tc.expectedErr != nil {
require.EqualError(t, err, tc.expectedErr.Error())
supplyAfter := nibiruApp.BankKeeper.GetSupply(ctx, "unibi")
require.EqualValues(t, tc.burnCoin, supplyBefore.Sub(supplyAfter))
Copy link
Contributor

Choose a reason for hiding this comment

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

The addition of supply checks before and after burning coins is a good practice for ensuring the correctness of the burn operation. However, there's a logical issue in the conditional block that checks for tc.expectedErr != nil. The supply comparison should occur outside this conditional block to ensure it's always executed, regardless of whether an error was expected or not. This ensures that the supply check is performed in all test scenarios.

-			if tc.expectedErr != nil {
-				require.EqualError(t, err, tc.expectedErr.Error())
-				supplyAfter := nibiruApp.BankKeeper.GetSupply(ctx, "unibi")
-				require.EqualValues(t, tc.burnCoin, supplyBefore.Sub(supplyAfter))
-			} else {
-				require.NoError(t, err)
-			}
+			if tc.expectedErr != nil {
+				require.EqualError(t, err, tc.expectedErr.Error())
+			} else {
+				require.NoError(t, err)
+			}
+			supplyAfter := nibiruApp.BankKeeper.GetSupply(ctx, "unibi")
+			require.EqualValues(t, tc.burnCoin, supplyBefore.Sub(supplyAfter))

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
supplyBefore := nibiruApp.BankKeeper.GetSupply(ctx, "unibi")
err := nibiruApp.InflationKeeper.Burn(ctx, sdk.NewCoins(tc.burnCoin), tc.sender)
if tc.expectedErr != nil {
require.EqualError(t, err, tc.expectedErr.Error())
supplyAfter := nibiruApp.BankKeeper.GetSupply(ctx, "unibi")
require.EqualValues(t, tc.burnCoin, supplyBefore.Sub(supplyAfter))
supplyBefore := nibiruApp.BankKeeper.GetSupply(ctx, "unibi")
err := nibiruApp.InflationKeeper.Burn(ctx, sdk.NewCoins(tc.burnCoin), tc.sender)
if tc.expectedErr != nil {
require.EqualError(t, err, tc.expectedErr.Error())
} else {
require.NoError(t, err)
}
supplyAfter := nibiruApp.BankKeeper.GetSupply(ctx, "unibi")
require.EqualValues(t, tc.burnCoin, supplyBefore.Sub(supplyAfter))

@k-yang
Copy link
Member

k-yang commented Mar 20, 2024

I ended up creating #1828 since I didn't realize you worked on it also.

I think we can close this in favor of #1828, since it contains all the test changes in this PR + negative test cases.

@Unique-Divine
Copy link
Member Author

Unique-Divine commented Mar 20, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

test(inflation-burn): Use bank total supply queries to validate state changes in MsgBurn
2 participants