migrate-tests

/migrate-tests

Migrates MCP tool tests from the old pattern to the new standardized pattern using test helpers.

Usage

/migrate-tests <test-folder-path>

Example:

/migrate-tests src/umbraco-api/tools/document-type/__tests__

Description

This command helps migrate MCP tool tests from the old pattern (JSON.parse with getResultText) to the new standardized pattern using validateStructuredContent, validateErrorResult, and createSnapshotResult.

Old vs New Patterns

Accessing Response Data

Old Pattern:

import { createMockRequestHandlerExtra, getResultText } from "@/test-helpers/create-mock-request-handler-extra.js";

const result = await Tool.handler(params, createMockRequestHandlerExtra());
const data = JSON.parse(getResultText(result));
expect(data.name).toBe("expected");

New Pattern:

import { createMockRequestHandlerExtra, validateStructuredContent } from "@/test-helpers/create-mock-request-handler-extra.js";
import { getEntityResponse } from "@/umbraco-api/umbracoManagementAPI.zod.js";

const result = await Tool.handler(params, createMockRequestHandlerExtra());
const data = validateStructuredContent(result, getEntityResponse);
expect(data.name).toBe("expected");

Validating Error Results

Old Pattern:

const result = await Tool.handler(params, createMockRequestHandlerExtra());
expect(result.isError).toBe(true);
// or check content[0].text for error message

New Pattern:

import { validateErrorResult } from "@/test-helpers/create-mock-request-handler-extra.js";

const result = await Tool.handler(params, createMockRequestHandlerExtra());
validateErrorResult(result);
expect(result).toMatchSnapshot();

Snapshot Testing

Old Pattern:

// Manual normalization of content[0].text
const normalizedResult = {
  ...result,
  content: result.content.map(content => {
    const parsed = JSON.parse((content as any).text);
    return {
      ...content,
      text: JSON.stringify({
        ...parsed,
        items: normalizeIds(parsed.items)
      })
    };
  })
};
expect(normalizedResult).toMatchSnapshot();