cdk-testing

Guidelines for testing AWS CDK code, where TypeScript defines cloud resources such as APIs and Lambda functions. The tests inspect the generated CloudFormation template, which describes those resources.

In plain words
What is it for?
Checking resource counts and settings, testing reusable CDK constructs, and using snapshot tests to compare generated infrastructure over time.
Why use it?
They catch missing or incorrectly configured cloud resources before deployment and help detect accidental infrastructure changes.

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/goranerhartic/cursor-development-rules/cdk-testing
Clone the repo
git clone --depth 1 https://github.com/GoranErhartic/cursor-development-rules

Made for: Cursor.

Per session 17 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,110 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.00017 $0.01110
Opus 5 $0.00009 $0.00555
Sonnet 5 $0.00003 $0.00222
Haiku 4.5 $0.00002 $0.00111

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

Security

Grade A, and why

cdk-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/languages/aws-lambda/cdk-testing.mdc · 155 lines

How it starts

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

CDK Testing

Overview

Test CDK stacks and constructs with aws-cdk-lib/assertions. Use Template.fromStack() to inspect synthesized CloudFormation and assert on resources. Use snapshot tests for regression safety.

Dependencies

pnpm add -D aws-cdk-lib vitest

Template Assertions

// cdk/lib/stacks/api-stack.test.ts

import { describe, it, expect } from "vitest";
import { App } from "aws-cdk-lib";
import { Template } from "aws-cdk-lib/assertions";
import { ApiStack } from "./api-stack";

describe("ApiStack", () => {
  it("should create a REST API and Lambda functions", () => {
    const app = new App();
    const stack = new ApiStack(app, "TestStack", {
      dataTable: createMockTable(),
      idempotencyTable: createMockTable(),
      databaseSecret: createMockSecret(),
      rdsProxyEndpoint: "proxy.example.com",
      opensearchEndpoint: "https://search.example.com",
    });

    const template = Template.fromStack(stack);

    template.resourceCountIs("AWS::ApiGateway::RestApi", 1);
    template.resourceCountIs("AWS::Lambda::Function", 3);

    template.hasResourceProperties("AWS::Lambda::Function", {
      Runtime: "nodejs22.x",
      Handler: "index.handler",
      MemorySize: 512,
      Timeout: 30,
    });

    template.hasResourceProperties("AWS::Lambda::Function", {
      Environment: {
        Variables: expect.objectContaining({
          DYNAMODB_TABLE_NAME: expect.any(String),
        }),
      },
    });
  });
});

function createMockTable() {
  return {} as any; // Use actual Table from a test stack or @aws-cdk-lib/aws-dynamodb
}
function createMockSecret() {
  return {} as any;
}

Fine-Grained Assertions

const template = Template.fromStack(stack);

// At least one Lambda with these properties
template.hasResourceProperties("AWS::Lambda::Function", {
  Runtime: "nodejs22.x",
  Architectures: ["arm64"],
});

// SQS event source with reportBatchItemFailures
template.hasResourceProperties("AWS::Lambda::EventSourceMapping", {
  EventSourceArn: expect.any(String),
  FunctionName: expect.any(String),
  BatchSize: 10,
});

// DynamoDB table with TTL
template.hasResourceProperties("AWS::DynamoDB::Table", {
  BillingMode: "PAY_PER_REQUEST",
  StreamSpecification: { StreamViewType: "NEW_AND_OLD_IMAGES" },
});

Read the full file on GitHub · 155 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 · 155 lines · 17 tokens per session scan A 51d83137f17b

Subscribe to this mod's changes

cdk-testing is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 1,110 once invoked, about $0.0001 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-30.