unit-testing-standards

A project rulebook for unit tests, which are small tests that check individual parts of a program.

In plain words
What is it for?
Use it when writing tests for Adobe AEM JavaScript features, including tests built with JUnit 5, Mockito, and AEM or Sling mock libraries.
Why use it?
It defines the testing tools, file locations, naming rules, setup, and cleanup patterns expected in the project.

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/adobecom/da-express-milo/unit-testing-standards
Clone the repo
git clone --depth 1 https://github.com/adobecom/da-express-milo

Made for: Cursor.

Per session 2,431 This file is loaded in full into every session.
When invoked 2,431 The same file — it is already loaded in full.
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.02431 $0.02431
Opus 5 $0.01215 $0.01215
Sonnet 5 $0.00486 $0.00486
Haiku 4.5 $0.00243 $0.00243

Measured 2d ago against content hash 954b923a0d49, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

unit-testing-standards 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/rules/unit-testing-standards.mdc · 389 lines

How it starts

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

Unit Testing Standards

APPLY: "Write my tests" queries

Testing Philosophy

Based on Adobe AEM unit testing best practices and community discussions:

Testing Framework Stack

  • JUnit 5: Primary testing framework
  • Mockito: Mock object creation and verification
  • wcm.io AEM Mocks: Mock AEM context and services
  • Apache Sling Mocks: Mock Sling abstractions

Test Structure Patterns

1. Standard Test File Organization

// ✅ REQUIRED: 1-to-1 mapping with source files
src/main/js/features/hero-marquee/hero-marquee.js
→ test/unit/features/hero-marquee/hero-marquee.test.js

// ✅ REQUIRED: Test suffix naming convention
// Allows easy identification and differentiation from source

2. Basic Test Structure

// ✅ STANDARD: Test structure pattern
describe('Hero Marquee Block', () => {
  let mockEl;
  
  beforeEach(() => {
    // Setup fresh DOM for each test
    document.body.innerHTML = '<div class="hero-marquee"></div>';
    mockEl = document.querySelector('.hero-marquee');
  });
  
  afterEach(() => {
    // Clean up DOM after each test
    document.body.innerHTML = '';
  });
  
  it('should create basic structure', () => {
    // Test the building blocks of functionality
    init(mockEl);
    expect(mockEl.querySelector('.foreground')).to.exist;
  });
  
  it('should handle missing content gracefully', () => {
    // Test edge cases and error conditions
    const emptyEl = document.createElement('div');
    init(emptyEl);
    expect(emptyEl.children.length).to.be.greaterThan(0);
  });
});

3. Testing Asynchronous Block Initialization

// ✅ REQUIRED: Test async block patterns
describe('Async Block Features', () => {
  it('should handle Promise.all data loading', async () => {
    const mockData = { cards: [], ratings: {} };
    
    // Mock async functions
    global.fetchCards = () => Promise.resolve(mockData.cards);
    global.fetchRatings = () => Promise.resolve(mockData.ratings);
    
    await init(mockEl);
    
    // Verify structure is created immediately (LCP optimization)
    expect(mockEl.querySelector('.headline')).to.exist;
    
    // Verify data enhancement happens after
    expect(mockEl.querySelector('.cards-container')).to.exist;
  });
  
  it('should not block LCP with API failures', async () => {
    // Mock API failure
    global.fetchCards = () => Promise.reject(new Error('API Error'));
    
    await init(mockEl);
    
    // Basic structure should still exist
    expect(mockEl.querySelector('.headline')).to.exist;
  });
});

Read the full file on GitHub · 389 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 · 389 lines · 2,431 tokens per session scan A 954b923a0d49

Subscribe to this mod's changes

unit-testing-standards is a cursor rule published in the GitHub repository adobecom/da-express-milo (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,431 tokens to every session, about $0.0122 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.