fix: Replace missing TicTacToe3D with existing CustomComponent in Com…

[dsarno]

…ponentResolver test

The TryResolve_PrefersPlayerAssemblies test was failing in CI because it referenced TicTacToe3D.cs which exists only locally and is not committed to the repository.

• Replace test reference from "TicTacToe3D" to "CustomComponent"
• CustomComponent exists in Assets/Scripts/TestAsmdef/ and is tracked in git
• CustomComponent is properly compiled into the TestAsmdef Player assembly
• Add explicit assertion to verify resolution from correct TestAsmdef assembly
• Test maintains same functionality: verifying ComponentResolver finds user scripts from Player assemblies

Summary by CodeRabbit

• Tests
  • Strengthened unit tests to ensure component resolution prefers Player assemblies over Editor assemblies.
  • Added stricter assertions on the source assembly to improve accuracy and prevent false positives.
  • Updated test component naming for clarity and consistency.
  • Improves test reliability and coverage with no impact to runtime behavior, helping catch regressions earlier.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Updated a unit test in ComponentResolverTests to use a different component name and add assertions ensuring the resolved type originates from the Player assembly named "TestAsmdef" and not an Editor assembly.

Changes

Cohort / File(s)	Summary of changes
EditMode Tests: Component resolution assertions TestProjects/UnityMCPTests/Assets/Tests/EditMode/Tools/ComponentResolverTests.cs	Modified TryResolve_PrefersPlayerAssemblies: changed component argument from "TicTacToe3D" to "CustomComponent"; added assertions verifying non-Editor assembly and exact assembly name "TestAsmdef".

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my whiskers, tests refine,
From TicTacToe to custom line—
Assemblies checked, Player true,
No Editor ghosts sneaking through.
With paws on keys, I stamp “OK,”
Hop along—green lights today! 🐇✅

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 65fdb4d and 8601c90.

📒 Files selected for processing (1)

• TestProjects/UnityMCPTests/Assets/Tests/EditMode/Tools/ComponentResolverTests.cs (2 hunks)

✨ 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.