feat(tests): core tools integration tests

[cte]

Related GitHub Issue

Closes: #

Description

Test Procedure

Type of Change

• 🐛 Bug Fix: Non-breaking change that fixes an issue.
• ✨ New Feature: Non-breaking change that adds functionality.
• 💥 Breaking Change: Fix or feature that would cause existing functionality to not work as expected.
• ♻️ Refactor: Code change that neither fixes a bug nor adds a feature.
• 💅 Style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
• 📚 Documentation: Updates to documentation files.
• ⚙️ Build/CI: Changes to the build process or CI configuration.
• 🧹 Chore: Other changes that don't modify src or test files.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Code Quality:
  • My code adheres to the project's style guidelines.
  • There are no new linting errors or warnings (npm run lint).
  • All debug code (e.g., console.log) has been removed.
• Testing:
  • New and/or updated tests have been added to cover my changes.
  • All tests pass locally (npm test).
  • The application builds successfully with my changes.
• Branch Hygiene: My branch is up-to-date (rebased) with the main branch.
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Changeset: A changeset has been created using npm run changeset if this PR includes user-facing changes or dependency updates.
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Documentation Updates

Additional Notes

Get in Touch

---

Important

Add comprehensive integration tests for Roo Code tools, including search_and_replace, search_files, use_mcp_tool, and write_to_file, to validate functionality and error handling.

• Integration Tests:
  • Add tests for search_and_replace in search-and-replace.test.ts to validate simple text replacement, regex pattern replacement, multiple matches, and no matches scenarios.
  • Add tests for search_files in search-files.test.ts to validate function definitions, TODO comments, file pattern filters, configuration keys, nested directories, complex regex patterns, and no matches scenarios.
  • Add tests for use_mcp_tool in use-mcp-tool.test.ts to validate MCP tool requests for read_file, write_file, list_directory, directory_tree, and error handling.
  • Add tests for write_to_file in write-to-file.test.ts to validate file creation with content and nested directory creation.
• Setup and Teardown:
  • Use suiteSetup, suiteTeardown, setup, and teardown hooks to manage test environments and clean up resources.
• Utilities:
  • Utilize waitFor and sleep from utils for asynchronous operations and state management.

^{This description was created by for 1f76576. You can customize this summary. It will automatically update as commits are pushed.}

[daniel-lxs]

It seems that the test is failing due to a bug with the terminal execution, the command is completion is not being picked up by Roo Code and so it times out the test.

This issue: #4384

[ellipsis-dev]

The event listener setup (e.g. messageHandler, taskStartedHandler, taskCompletedHandler) is repeated in many test files. For better maintainability, consider refactoring this repeated code into shared utility functions.

^{This comment was generated because it violated a code review rule: irule_tTqpIuNs8DV0QFGj.}

[cte]

This is awesome; I think we can merge this as soon as the tests pass in CI and we can continue to iterate on the mode. I can't approve the PR since I'm the author (not exactly sure how that happened).

[daniel-lxs]

@cte
Sounds good! The test is showing a bug that is reported here #4384.

Until that is fixed and this branch is rebased the test will fail.

[daniel-lxs]

Disabling shell integration fixed the issue.

LGTM