nala-test-generation

A set of rules for generating end-to-end tests with Nala, a testing framework for checking complete web pages and user interactions. The examples use Playwright to open pages and verify their visible elements and links.

In plain words
What is it for?
Use it when asked to generate Nala tests or end-to-end tests for Adobe Experience Manager Edge Delivery Services pages. It covers page loading, block visibility, content checks, and call-to-action links.
Why use it?
Writing repeated browser tests by hand can lead to inconsistent coverage. These rules provide a standard structure for checking blocks, headlines, buttons, and other page 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/adobecom/express-milo/nala-test-generation
Clone the repo
git clone --depth 1 https://github.com/adobecom/express-milo

Made for: Cursor.

Per session 3,752 This file is loaded in full into every session.
When invoked 3,752 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.03752 $0.03752
Opus 5 $0.01876 $0.01876
Sonnet 5 $0.00750 $0.00750
Haiku 4.5 $0.00375 $0.00375

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

Security

Grade A, and why

nala-test-generation 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 3d 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

This is a copy

100% identical to nala-test-generation — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/nala-test-generation.mdc · 513 lines

How it starts

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

Nala E2E Test Generation Standards

APPLY: "Generate Nala tests" or "Write E2E tests" queries

Automated Nala Test Generation

Based on the Nala Testing Framework, this rule generates comprehensive end-to-end tests for AEM Edge Delivery Services blocks and pages.

Test Generation Patterns

1. Block-Level Test Structure

// ✅ STANDARD: Generated Nala test for blocks
import { test, expect } from '@playwright/test';

test.describe('[BlockName] Block Tests', () => {
  test.beforeEach(async ({ page }) => {
    await page.goto('/express/');
    await page.waitForLoadState('networkidle');
  });

  test('should display core elements correctly', async ({ page }) => {
    const block = page.locator('.block-name');
    await expect(block).toBeVisible();
    
    // Test headline presence and content
    const headline = block.locator('h1, h2, h3').first();
    await expect(headline).toBeVisible();
    await expect(headline).not.toBeEmpty();
    
    // Test CTA functionality
    const cta = block.locator('.cta a, .button').first();
    if (await cta.count() > 0) {
      await expect(cta).toBeVisible();
      await expect(cta).toHaveAttribute('href');
    }
  });

  test('should be accessible', async ({ page }) => {
    const block = page.locator('.block-name');
    
    // Check ARIA labels and semantic structure
    await expect(block.locator('h1, h2, h3')).toHaveCount(1); // One main heading
    
    // Check keyboard navigation
    await page.keyboard.press('Tab');
    const focusedElement = page.locator(':focus');
    await expect(focusedElement).toBeVisible();
  });

  test('should be responsive', async ({ page }) => {
    const block = page.locator('.block-name');
    
    // Mobile viewport
    await page.setViewportSize({ width: 375, height: 667 });
    await page.reload();
    await expect(block).toBeVisible();
    
    // Tablet viewport
    await page.setViewportSize({ width: 768, height: 1024 });
    await page.reload();
    await expect(block).toBeVisible();
    
    // Desktop viewport
    await page.setViewportSize({ width: 1200, height: 800 });
    await page.reload();
    await expect(block).toBeVisible();
  });
});

Read the full file on GitHub · 513 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. 3d ago First seen · 513 lines · 3,752 tokens per session scan A 9394feba1ac5

Subscribe to this mod's changes

nala-test-generation is a cursor rule published in the GitHub repository adobecom/express-milo (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3,752 tokens to every session, about $0.0188 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to nala-test-generation, differing in 2 lines, and is treated as a copy.