refactor test to lock behavior of SendTokenIBC

[tuantran1702]

1. Summary

Fixes #1517

2.Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

3. Implementation details

4. How to test/use

5. Checklist

• Does the Readme need to be updated?

6. Limitations (optional)

7. Future Work (optional)

Summary by CodeRabbit

• Tests
  • Improved the setup logic for channel sequences in interchain staking tests to enhance reliability and prevent regressions.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
quicksilver	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 30, 2024 2:32pm

[coderabbitai]

Walkthrough

The update in the receipt_test.go file involves modifying the setup for interchain staking channel sequences. This change ensures counterparty channel sequences are set before the transfer channels are created, enhancing the robustness of the system by avoiding potential regressions related to channel sequence conflicts.

Changes

File Path	Change Summary
.../keeper/receipt_test.go	Adjusted the setup of channel sequences to set counterparty channel sequence before creating transfer channels.

Possibly related issues

• [InterchainTest] Set up interchaintest for HandleTokenizedShares function #751: This issue discusses setting up tests for a specific function in interchain staking. Although it focuses on a different function (HandleTokenizedShares), the emphasis on robust test setups in the interchain staking context could potentially benefit from insights or methods developed in the addressed PR change.

Poem

🐇✨
In the realm of code where sequences intertwine,
A rabbit hops along, making channels align.
With a tweak here and there, in the test bed,
Ensures no regression makes its dreadful spread.
🌟🌿 Happy coding, let the channels flow! 🌿🌟

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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/schema.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.

[joe-bowman]

This pull request has been deployed to Vercel.

Latest commit:	6b9ded3
✅ Preview:	https://pr-1518.app-dev.quicksilver.zone
🔍 Inspect:	https://vercel.com/quicksilver/quicksilver/64dpqfT4PefN8kHPshHfXLKovBnw

View Workflow Logs

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 62.97%. Comparing base (2139cd6) to head (b70eaa8).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1518   +/-   ##
=======================================
  Coverage   62.97%   62.97%           
=======================================
  Files         192      192           
  Lines       13495    13495           
=======================================
  Hits         8499     8499           
  Misses       4181     4181           
  Partials      815      815           

Flag	Coverage Δ
unittests	62.97% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.