add manager service client mocks

[WashingtonKK]

What type of PR is this?

What does this do?

Which issue(s) does this PR fix/relate to?

• Related Issue #
• Resolves #

Have you included tests for your changes?

Did you document any new/modified feature?

Notes

Summary by CodeRabbit

• New Features

  • Added mock implementation for ManagerServiceClient to support testing
  • Introduced configuration for generating mock service client in test environments

• Chores

  • Updated mockery configuration to support new mock generation process

[coderabbitai]

Walkthrough

The pull request introduces a mock implementation for the ManagerServiceClient interface in the manager/mocks directory. This mock client is generated using the mockery tool and provides a comprehensive testing framework for simulating the behavior of the actual ManagerServiceClient. The implementation includes methods for various service operations like AttestationPolicy, CreateVm, RemoveVm, and SVMInfo, enabling developers to create detailed test scenarios with precise control over method calls and return values.

Changes

File	Change Summary
manager/mocks/manager_service_client.go	Added mock implementation of ManagerServiceClient with methods for AttestationPolicy, CreateVm, RemoveVm, and SVMInfo
mockery.yml	Added configuration for generating ManagerServiceClient mock, specifying directory, filename, and mock name

Poem

🐰 A Mock Rabbit's Delight 🥕

In tests where services dance and sway,
Our mock client finds its playful way
Simulating calls with mock finesse
No real service? No more stress!
Testing made simple, oh what glee! 🧪

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

CodeRabbit Configuration 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

manager/mocks/manager_service_client.go (1)

43-45: Enhance panic messages with method parameter details.

The panic messages could be more helpful by including the method parameters in the error message. This would make debugging easier when a mock expectation is not properly set up.

Example improvement for AttestationPolicy:

-		panic("no return value specified for AttestationPolicy")
+		panic(fmt.Sprintf("no return value specified for AttestationPolicy(ctx: %v, req: %+v, opts: %v)", ctx, in, opts))

Also applies to: 117-119, 191-193, 265-267

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 58b401e and abc5449.

📒 Files selected for processing (2)

• manager/mocks/manager_service_client.go (1 hunks)
• mockery.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: ci

🔇 Additional comments (4)

manager/mocks/manager_service_client.go (3)

1-18: LGTM! The file header and imports look good.

The file includes appropriate copyright notice, license information, and all necessary imports for the mock implementation.

---

19-30: LGTM! The mock structure definitions are well-implemented.

The structures follow the standard mockery pattern with proper embedding of mock.Mock and expecter implementation.

---

328-340: LGTM! The constructor is well-implemented.

The NewManagerServiceClient constructor follows best practices:

• Uses a generic interface for testing.T compatibility
• Properly initializes the mock
• Registers cleanup function to assert expectations

mockery.yml (1)

65-69: LGTM! The mockery configuration is properly structured.

The new configuration for ManagerServiceClient follows the established pattern and is correctly placed within the github.com/ultravioletrs/cocos/manager package section.