Make MCP configurations unit-test more specific

[umago]

Description

Every time a configuration is added the
test_dump_configuration_with_more_mcp_servers() and test_dump_configuration_with_one_mcp_server() are affected, it shouldn't be the case since these tests should be focused on the MCP configuration.

For a general configuration test we already have the test_dump_configuration().

This patch changes the MCP tests to be more focused on what they are really asserting instead of a general configuration test that is already covered as part of test_dump_configuration().

Type of change

• Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up service version
• Bump-up dependent library
• Bump-up library or tool used for development (does not change the final image)
• CI configuration change
• Konflux configuration change
• Unit tests improvement
• Integration tests improvement
• End to end tests improvement

Related Tickets & Documents

• Related Issue #
• Closes #

Checklist before requesting a review

• I have performed a self-review of my code.
• PR has passed all pre-merge test jobs.
• If it is a core feature, I have added thorough tests.

Testing

• Please provide detailed steps to perform tests related to this code change.
• How were the fix/results from this change verified? Please provide relevant screenshots or results.

Summary by CodeRabbit

• Tests
  • Updated unit tests to focus on verifying the mcp_servers configuration, removing checks for other configuration sections.

[coderabbitai]

Walkthrough

Two unit tests in the configuration model test suite were updated to exclude the inference configuration from their setup and assertions. The tests now focus solely on verifying the correctness of the mcp_servers list in the dumped configuration JSON, omitting checks for other configuration sections.

Changes

File(s)	Change Summary
tests/unit/models/test_config.py	Updated two tests to set inference=None and simplified assertions to only check mcp_servers.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

In the warren of code, two tests did hop,
No more "inference"—they gave it a stop.
Now only mcp_servers get their due,
Simpler checks, and faster too!
With JSON neat and rabbits fleet,
Our test suite’s trim—oh, what a treat! 🐇

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c1c7ba3 and daeb64f.

📒 Files selected for processing (1)

• tests/unit/models/test_config.py (4 hunks)

🔇 Additional comments (4)

tests/unit/models/test_config.py (4)

577-577: Good refactoring to improve test isolation.

Setting inference=None removes the dependency on InferenceConfiguration from this MCP-focused test, making it more specific and maintainable as intended.

---

591-598: Excellent focus on MCP-specific assertions.

The refactored assertion now targets only the mcp_servers configuration, eliminating unnecessary dependencies on other configuration sections and making the test more maintainable.

---

628-628: Consistent refactoring for test isolation.

Like the previous test, removing the inference configuration dependency keeps this test focused solely on MCP server functionality.

---

648-665: Well-structured focused assertion for multiple MCP servers.

The refactored assertion properly validates all three MCP servers while maintaining focus only on MCP configuration, completing the test specificity improvements outlined in the PR objectives.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this 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.

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.

[tisnik]

It looks ok, thank you