testing

A set of project rules for testing JavaScript code with Jest, a JavaScript testing framework. It defines test locations, response checks, mocking patterns, and nested test structure.

In plain words
What is it for?
It is for writing Jest tests for handlers and modules, especially code using a Microsoft Graph client.
Why use it?
It gives tests a consistent structure and explains how to mock dependencies and check success or error responses.

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/titanzero/outlook-mcp/testing
Clone the repo
git clone --depth 1 https://github.com/titanzero/outlook-mcp

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 437 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin fork From a forked repository.
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.00000 $0.00437
Opus 5 $0.00000 $0.00218
Sonnet 5 $0.00000 $0.00087
Haiku 4.5 $0.00000 $0.00044

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

Security

Grade A, and why

testing 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.mdc · 69 lines

What it actually says

Testing Rules

Framework

Jest (npm test). Tests live in test/ mirroring source structure:

  • email/list.jstest/email/list.test.js
  • auth/token-manager.jstest/auth/token-manager.test.js

Response Format in Tests

Tests assert against plain-text output. Set text mode at the top of every test file before imports:

process.env.OUTLOOK_RESPONSE_FORMAT = 'text';

Mock Pattern

Mock the Graph client and any module-level dependencies:

const { getGraphClient, graphGetPaginated } = require('../../utils/graph-client');
jest.mock('../../utils/graph-client');

const mockClient = {};
beforeEach(() => {
  jest.clearAllMocks();
  jest.spyOn(console, 'error').mockImplementation(() => {});
  getGraphClient.mockResolvedValue(mockClient);
});
afterEach(() => {
  console.error.mockRestore();
});

Assertion Style

  • Check result.content[0].text for response content
  • Check result.isError for error responses
  • Verify mock call arguments with expect.objectContaining()

Test Structure

Use nested describe blocks:

describe('handlerName', () => {
  describe('successful operation', () => { ... });
  describe('empty results', () => { ... });
  describe('error handling', () => {
    test('should handle authentication error', ...);
    test('should handle Graph API error', ...);
  });
});

Auth Error Testing

test('should handle authentication error', async () => {
  const authError = new Error('Authentication required');
  authError.isAuthError = true;
  getGraphClient.mockRejectedValue(authError);

  const result = await handler({});
  expect(result.isError).toBe(true);
  expect(result.content[0].text).toBe('Authentication required');
});
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 · 69 lines · 0 tokens per session scan A 08653d3a4ecf

Subscribe to this mod's changes

testing is a cursor rule published in the GitHub repository titanzero/outlook-mcp (1 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 437 tokens. A static security scan graded it A with 0 findings. It comes from a forked repository.