testing

A set of testing rules for XM Cloud starter applications. XM Cloud is Sitecore's cloud platform for managing website content.

In plain words
What is it for?
Use it to plan component, integration, end-to-end, accessibility, responsive, and API tests with tools such as Jest, Vitest, Playwright, or Cypress.
Why use it?
It helps developers check that pages and components handle different content, failures, editing modes, APIs, builds, and deployments correctly.

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/sitecore/xmcloud-starter-js/testing
Clone the repo
git clone --depth 1 https://github.com/Sitecore/xmcloud-starter-js

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,257 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.00000 $0.01257
Opus 5 $0.00000 $0.00629
Sonnet 5 $0.00000 $0.00251
Haiku 4.5 $0.00000 $0.00126

Measured 2d ago against content hash e0c3b8b6b249, 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 2d ago.

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 · 204 lines

How it starts

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

Testing Patterns

Testing Strategy

Component Testing:

  • Test component rendering with various XM Cloud field configurations
  • Mock XM Cloud services and API calls
  • Test error scenarios (missing fields, API failures)
  • Verify proper handling of editing vs. preview modes
  • Test responsive behavior and accessibility

Integration Testing:

  • Test complete page rendering with XM Cloud data
  • Verify API route functionality
  • Test middleware behavior for XM Cloud integration
  • Validate environment variable handling
  • Test deployment and build processes

Testing Tools

Recommended Stack:

  • Jest or Vitest for unit testing
  • React Testing Library for component testing
  • MSW (Mock Service Worker) for API mocking
  • Playwright or Cypress for E2E testing
  • Storybook for component documentation and testing

XM Cloud Mocking:

  • Create mock data that matches XM Cloud field structures
  • Mock layout service responses
  • Simulate both connected and disconnected modes
  • Test with various content scenarios
// Mock XM Cloud field data
const mockHeroFields = {
  title: { value: 'Test Hero Title', editable: false },
  subtitle: { value: 'Test Hero Subtitle', editable: false },
  backgroundImage: {
    value: {
      src: '/test-image.jpg',
      alt: 'Test Image',
      width: 1200,
      height: 600,
    },
    editable: false,
  },
};

Component Testing Patterns

Field Validation Testing:

  • Test components with missing fields
  • Test components with empty field values
  • Test components with various field types
  • Verify proper fallback rendering
// Component test example
describe('Hero Component', () => {
  it('renders with all fields present', () => {
    render(<Hero fields={mockHeroFields} />);
    
    expect(screen.getByText('Test Hero Title')).toBeInTheDocument();
    expect(screen.getByText('Test Hero Subtitle')).toBeInTheDocument();
    expect(screen.getByRole('img')).toHaveAttribute('alt', 'Test Image');
  });
  
  it('handles missing fields gracefully', () => {
    render(<Hero fields={{}} />);
    
    expect(screen.getByText(/content not configured/i)).toBeInTheDocument();
  });
});

Read the full file on GitHub · 204 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. 2d ago First seen · 204 lines · 0 tokens per session scan A e0c3b8b6b249

Subscribe to this mod's changes

testing is a cursor rule published in the GitHub repository Sitecore/xmcloud-starter-js (29 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,257 tokens. 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-30.