test(precompiles): add missing test in staking

[fbac]

Description

Add missings tests for stake, unstake and moveStake. All these functions should fail if called through staticcall (readOnly = true).

This PR has to be merged before #3010

How Has This Been Tested?

• Tested CCTX in localnet
• Tested in development environment
• Go unit tests
• Go integration tests
• Tested via GitHub Actions

Summary by CodeRabbit

• Tests
  • Introduced new test cases for staking, unstaking, and moving stake functionalities in read-only mode.
  • Enhanced error handling to ensure appropriate error messages are raised during restricted operations.
  • Maintained consistent test structure for improved clarity and feedback on operations.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes in this pull request enhance the test suite for the IStakingContract by introducing new test cases that validate the contract's behavior in read-only mode. Specifically, tests for staking, unstaking, and moving stakes have been added to ensure that these operations correctly fail when the contract is in read-only mode. Additionally, error handling assertions have been implemented to confirm that appropriate errors are raised under these conditions, thereby improving the robustness of the tests.

Changes

File Path	Change Summary
precompiles/staking/staking_test.go	Added new test cases for Test_Stake, Test_Unstake, and Test_MoveStake to check failures in read-only mode. Enhanced error handling with assertions for correct error messages.

Possibly related PRs

• fix: calling precompile through sc with sc state update #2853: Modifies the TestStaking contract and associated files, potentially relating to the newly added test cases for staking operations.
• feat: emit events from staking precompile #2861: Introduces event emissions for staking operations, relevant to the main PR's focus on testing staking function behavior.
• refactor(precompile): do not execute write functions on staticcall #3001: Refactors the Run method to prevent write operations in read-only mode, directly connecting to the enhancements tested in this PR.

Suggested labels

UPGRADE_TESTS, TSS_MIGRATION_TESTS

Suggested reviewers

• swift1337
• kingpinXD
• ws4charlie
• brewmaster012
• skosito
• lumtis

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[coderabbitai]

Actionable comments posted: 6

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 250b90e and e67bcc9.

📒 Files selected for processing (1)

• precompiles/staking/staking_test.go (4 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

precompiles/staking/staking_test.go (1)

Pattern **/*.go: Review the Go code, point out issues relative to principles of clean code, expressiveness, and performance.

🔇 Additional comments (1)

precompiles/staking/staking_test.go (1)

26-26: Import statement added appropriately

The import of ptypes is correctly added to handle error types related to precompile methods.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.29%. Comparing base (250b90e) to head (05610a1).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3017      +/-   ##
===========================================
+ Coverage    66.25%   66.29%   +0.03%     
===========================================
  Files          406      406              
  Lines        22772    22772              
===========================================
+ Hits         15088    15097       +9     
+ Misses        6907     6901       -6     
+ Partials       777      774       -3     

see 1 file with indirect coverage changes