testing-conventions

A set of testing rules for a Strapi MCP plugin, using Vitest, a JavaScript and TypeScript test runner. It defines test file locations, behavior-focused test structure, lightweight fakes, and ways to test MCP tools, controllers, and services.

In plain words
What is it for?
Use it when adding or reviewing unit tests, MCP tool tests, controller tests, or service tests in the Strapi plugin.
Why use it?
It gives contributors a consistent way to test the plugin without starting a real Strapi application for every test. This makes tests focused on inputs, outputs, and behavior.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/virtuslab-open-source/strapi-plugin-mcp/testing-conventions
Clone the repo
git clone --depth 1 https://github.com/VirtusLab-Open-Source/strapi-plugin-mcp

Made for: Cursor.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,043 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00009 $0.01043
Opus 5 $0.00005 $0.00522
Sonnet 5 $0.00002 $0.00209
Haiku 4.5 $0.00001 $0.00104

Measured yesterday against content hash 4e3c356b73f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

testing-conventions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/testing-conventions.mdc · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing Conventions & Techniques

Overview

  • Test runner: Vitest (pnpm test, pnpm test:run, pnpm coverage).
  • Test files: **/*.spec.ts or **/*.test.ts colocated with code or under server/test.
  • Style: Given/When/Then sections with comments. Behavior-oriented test names.

Structure and Patterns

  • Unit tests: Target pure logic in services and tool callbacks. Avoid real Strapi.
  • MCP tools: Build tool via its builder with a mock strapi, call callback(args, ctx).
  • Controllers: Keep minimal; test they delegate and shape responses correctly.
  • Services: Assert inputs/outputs; use dependency injection for collaborators.

Strapi Mocking

  • Prefer lightweight fakes over deep mocks. Use server/test/strapi.mock.ts for content types/components.
  • For specialized cases, create ad-hoc mocks with only required surface:
const strapi = {
  config: { get: vi.fn(() => 'value') },
  services: { 'api::blog.post': {}, 'plugin::mcp.services': {} },
} as unknown as Strapi;

MCP Tool Testing Recipe

  1. Build tool: const tool = getXTool(strapi);
  2. Validate metadata: name, description, argsSchema (Zod parse with valid/invalid payloads).
  3. Invoke: const res = await tool.callback(args as any, {} as any);
  4. Extract payload: const text = (res.content?.[0] as any)?.text; const json = JSON.parse(text ?? '{}');
  5. Assert json shape: success/isSuccess, data fields, and error messages for negative paths.

Example:

it('returns services list', async () => {
  // Given
  const strapi = { services: { 'api::blog.post': {}, 'plugin::mcp.services': {} } } as any;
  const tool = getServicesTool(strapi);

  // When
  const res = await tool.callback({}, {} as any);

  // Then
  const payload = JSON.parse((res.content?.[0] as any).text ?? '{}');
  expect(payload.success).toBe(true);
  expect(payload.services).toEqual(
    expect.arrayContaining([
      expect.objectContaining({ fullQualifiedName: 'api::blog.post', type: 'internal', name: 'post' }),
      expect.objectContaining({ fullQualifiedName: 'plugin::mcp.services', type: 'plugin', name: 'services', plugin: 'mcp' }),
    ])
  );
});

Read the full file on GitHub · 107 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 107 lines · 9 tokens per session scan A 4e3c356b73f3

Subscribe to this mod's changes

testing-conventions is a cursor rule published in the GitHub repository VirtusLab-Open-Source/strapi-plugin-mcp (3 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 1,043 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.