Skip to content

Add mocked tests for MCP tool modules #3

Description

@MattyMailers

Goal

Expand mocked Vitest coverage across the MCP tool modules so contributors can safely add endpoints without breaking path/query/body contracts.

Suggested scope

  • Mock SmartMovingClient for one tool module at a time.
  • Assert endpoint paths and query casing.
  • Assert create/update request body shape.
  • Assert API failures return isError: true.
  • Use fake data only.

Good first module choices

  • reference.ts
  • communication.ts
  • followups.ts

Done when

  • At least one tool module has meaningful mocked tests.
  • npm run verify passes.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood issue for a first contributionhelp wantedUseful contribution from the communitytestsTesting or verification improvements

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions