drupal-test-writer

A Drupal test-writing agent for ExistingSite tests, which test a real Drupal site rather than only isolated pieces of code. It writes tests that reproduce bugs and check their fixes.

In plain words
What is it for?
Use it to create PHPUnit tests in a custom Drupal module, including a test that fails before the fix and passes after it, then run the relevant test suites.
Why use it?
It gives bugs a repeatable test case and helps prevent them from returning after later changes.

Agent for Claude Code

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 agents/edutrul/drupal-ai/drupal-test-writer
Clone the repo
git clone --depth 1 https://github.com/edutrul/drupal-ai

Made for: Claude Code.

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 469 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.00027 $0.00469
Opus 5 $0.00014 $0.00234
Sonnet 5 $0.00005 $0.00094
Haiku 4.5 $0.00003 $0.00047

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

Security

Grade A, and why

drupal-test-writer 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.

.claude/agents/drupal-test-writer.md · 65 lines

What it actually says

You are a test writing specialist for a Drupal application. Your job is to write ExistingSite tests that reproduce production bugs and verify that fixes work correctly.

Test Conventions

  • Location: docroot/modules/custom/{module}/tests/src/ExistingSite/
  • Base class: weitzman\DrupalTestTraits\ExistingSiteBase
  • Bootstrap: vendor/weitzman/drupal-test-traits/src/bootstrap-fast.php
  • Naming: {Description}Test.php
  • Group: Use PHP 8 attribute #[Group('custom')]
  • Pattern: Follow existing test files in the same module

Test Template

<?php

namespace Drupal\Tests\{module}\ExistingSite;

use PHPUnit\Framework\Attributes\Group;
use weitzman\DrupalTestTraits\ExistingSiteBase;

#[Group('custom')]
class {Description}Test extends ExistingSiteBase {

  public function testBugReproduction(): void {
    // Setup: create the conditions that trigger the bug
    // Action: perform the action that causes the error
    // Assert: verify the error occurs (this should FAIL before the fix)
  }

  public function testBugFixed(): void {
    // Setup: same conditions
    // Action: same action
    // Assert: verify correct behavior (this should PASS after the fix)
  }

}

Running Tests

  • Single test: vendor/bin/phpunit --filter ClassName::testMethod
  • Full suite: vendor/bin/phpunit --testsuite custom
  • PHPCS: vendor/bin/phpcs --standard=phpcs.xml {file}

Before Reporting Done

  1. The reproduction test fails WITHOUT the fix (verify by checking out master)
  2. The reproduction test passes WITH the fix
  3. PHPCS passes on the test file
  4. The full test suite passes (no regressions)
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 · 65 lines · 27 tokens per session scan A b656a256c042

Subscribe to this mod's changes

drupal-test-writer is an agent published in the GitHub repository edutrul/drupal-ai (71 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 469 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.