testing-strategy

A set of rules for writing software tests, including unit tests for small pieces and integration tests for connected parts such as an API and database.

In plain words
What is it for?
Use it to plan and write unit and integration tests, choose what to mock, prepare test data, and verify application behavior.
Why use it?
It helps tests stay readable, reliable, and useful by covering naming, mocks, test data, cleanup, and coverage.

Cursor rule

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/jahands/prompts/testing-strategy
Clone the repo
git clone --depth 1 https://github.com/jahands/prompts
Per session 22 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,658 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.00022 $0.01658
Opus 5 $0.00011 $0.00829
Sonnet 5 $0.00004 $0.00332
Haiku 4.5 $0.00002 $0.00166

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

Security

Grade A, and why

testing-strategy 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/test-rules/testing-strategy.mdc · 262 lines

How it starts

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

Guidelines for writing maintainable, reliable tests across all levels - from unit tests to integration tests. Emphasizes test structure, naming clarity, appropriate mocking, and effective test data management.

  const userData = createUserData({ email: '[email protected]' });
  passwordHasher.hash.mockResolvedValue('hashed-password');
  
  // Act
  const result = await service.createUser(userData);
  
  // Assert
  expect(result.email).toBe('[email protected]');
  expect(passwordHasher.hash).toHaveBeenCalledWith(userData.password);
  expect(mockRepository.save).toHaveBeenCalledWith(
    expect.objectContaining({ password: 'hashed-password' })
  );
});

}); });

</example>

<example type="integration-test">
```typescript
describe('User API Integration', () => {
  let app: Application;
  let database: TestDatabase;
  
  beforeAll(async () => {
    database = await TestDatabase.create();
    app = createApp(database);
  });
  
  afterAll(async () => {
    await database.cleanup();
  });
  
  describe('POST /users', () => {
    it('User_Registration_CreatesUserAndReturnsToken', async () => {
      // Arrange
      const newUser = {
        email: '[email protected]',
        password: 'SecurePass123!',
        name: 'Test User'
      };
      
      // Act
      const response = await request(app)
        .post('/users')
        .send(newUser);
      
      // Assert
      expect(response.status).toBe(201);
      expect(response.body).toMatchObject({
        user: { email: newUser.email, name: newUser.name },
        token: expect.any(String)
      });
      
      // Verify persistence
      const savedUser = await database.users.findByEmail(newUser.email);
      expect(savedUser).toBeDefined();
      expect(savedUser.password).not.toBe(newUser.password); // Should be hashed
    });
  });
});

Read the full file on GitHub · 262 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 · 262 lines · 22 tokens per session scan A e5787dcd1c7f

Subscribe to this mod's changes

testing-strategy is a cursor rule published in the GitHub repository jahands/prompts (19 stars, last pushed 7mo ago), licensed MIT. It adds 22 tokens to every session and 1,658 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.