write-tests

Guidance for writing backend tests, including tests that use a real PostgreSQL database and smaller tests for self-contained logic.

In plain words
What is it for?
Plan and write service-level database tests, table-based unit tests, and test data setup after reviewing a module's documented test scenarios.
Why use it?
It helps check what the software promises, including error cases, instead of only checking how the code is written.

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/golid-ai/golid/write-tests
Clone the repo
git clone --depth 1 https://github.com/golid-ai/golid

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,267 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.00000 $0.01267
Opus 5 $0.00000 $0.00633
Sonnet 5 $0.00000 $0.00253
Haiku 4.5 $0.00000 $0.00127

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

Security

Grade A, and why

write-tests 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/write-tests.mdc · 131 lines

How it starts

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

Writing Backend Tests

Thesis: Test the contract, not the implementation. Integration tests hit real PostgreSQL; unit tests are table-driven; every service method has error path coverage.

Before writing tests for a module, read docs/modules/{module}/spec.md for the Critical Test Scenarios section — it's a verified test plan.

Integration Tests (Service Layer)

Test real SQL against a real PostgreSQL instance using testutil.WithTestDB.

//go:build integration

package service_test

import (
    "testing"
    "github.com/golid-ai/golid/backend/internal/service"
    "github.com/golid-ai/golid/backend/internal/testutil"
)

func TestItemService_Create(t *testing.T) {
    testutil.WithTestDB(t, func(pool *pgxpool.Pool) {
        svc := service.NewItemService(pool, 20, 100)

        // Seed prerequisite data with raw SQL
        _, err := pool.Exec(ctx, `INSERT INTO users (...) VALUES (...)`)
        // ...

        // Test the service method
        result, err := svc.Create(ctx, &service.CreateItemInput{...})
        if err != nil { t.Fatalf("expected no error, got %v", err) }
        if result.Title != "Test Item" { t.Errorf("expected title 'Test Item', got %s", result.Title) }
    })
}

Key Rules

  • Build tag: //go:build integration at the top of the file.
  • File naming: x_integration_test.go (not x_test.go) to make it clear.
  • Seed with raw SQL: Use pool.Exec with INSERT statements. Never use service methods to seed — they have their own validation and side effects.
  • Test one thing per function: Each test function should test one behavior (happy path, error case, permission check, etc.).
  • Clean state: WithTestDB provides a fresh database for each test. No cleanup needed.

What to Test

  • Happy paths: Create, Read, Update, Delete with valid inputs.
  • Permission checks: Wrong user type, non-owner, non-member. Expect FORBIDDEN.
  • Status guards: Operation on wrong-status parent. Expect BAD_REQUEST.
  • Not found: Non-existent ID. Expect NOT_FOUND.
  • Conflict: Duplicate entries. Expect CONFLICT.
  • Edge cases: Empty arrays, null optional fields, boundary values.

Read the full file on GitHub · 131 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 · 131 lines · 0 tokens per session scan A b839c032001c

Subscribe to this mod's changes

write-tests is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,267 tokens. 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.