Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/managing-database-tests

@820dfc8
Run it yourself

Test database testing including fixtures, transactions, and rollback management. Use when performing specialized testing. Trigger with phrases like "test the database", "run database tests", or "validate data integrity".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/managing-database-tests

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈61 tokens for metadata: the name and description. ≈1.8k when used: this file. ≈2.8k more on demand in 6 files.

Description uses 3.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈246 characters, or 3.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Database Test Manager

Overview

Manage database testing including fixture loading, transaction-based test isolation, migration validation, query performance testing, and data integrity checks. Supports PostgreSQL, MySQL, MongoDB, SQLite (in-memory), and Redis with ORM-agnostic patterns for Prisma, TypeORM, SQLAlchemy, Knex, and Drizzle.

Prerequisites

  • Database instance available for testing (Docker container, in-memory SQLite, or dedicated test server)
  • Database client library and ORM installed (Prisma, TypeORM, Knex, SQLAlchemy, etc.)
  • Migration files up to date and tested independently
  • Test database connection string configured in environment (distinct from development/production)
  • Database seed data scripts for baseline test state

Instructions

  1. Set up the test database infrastructure:
    • Use Docker to spin up a dedicated test database: docker run -d -p 5433:5432 --name test-db postgres:16-alpine.
    • Or use SQLite in-memory mode for fast unit tests: sqlite::memory:.
    • Or use Testcontainers for ephemeral database per test suite.
    • Verify the test database is isolated from development data.
  2. Run database migrations against the test database:
    • Execute npx prisma migrate deploy or npx knex migrate:latest --env test.
    • Verify all migrations apply cleanly to an empty database.
    • Test rollback: run migrate:rollback and verify schema reverts correctly.
  3. Implement test isolation strategy (choose one):
    • Transaction rollback: Wrap each test in a transaction; roll back after assertions. Fastest option.
    • Truncation: Truncate all tables in beforeEach. Simpler but slower.
    • Database recreation: Drop and recreate the database before each test suite. Slowest, most thorough.
  4. Create database fixture utilities:
    • Factory functions that insert records and return the created entity with its database-generated ID.
    • Seed functions for standard test scenarios (empty state, populated state, edge cases).
    • Cleanup utilities that handle foreign key ordering for truncation.
  5. Write database-specific test cases:
    • CRUD operations: Insert, query, update, delete records and verify database state.
    • Constraint validation: Attempt invalid inserts (null on NOT NULL, duplicate on UNIQUE) and verify rejection.
    • Referential integrity: Verify cascading deletes, foreign key enforcement, and orphan prevention.
    • Index performance: Verify queries use expected indexes with EXPLAIN ANALYZE.
    • Transaction isolation: Test concurrent updates and verify conflict handling.
  6. Test database query performance:
    • Run EXPLAIN ANALYZE on critical queries and assert expected index usage.
    • Benchmark query execution time with representative data volumes.
    • Flag queries doing sequential scans on large tables.
  7. Validate migration safety:
    • Test each migration can run on a populated database without data loss.
    • Verify backward compatibility (old code works with new schema during rollout).
    • Check migration execution time is acceptable for production deployment.

Output

  • Database test files organized by entity in tests/database/ or tests/models/
  • Fixture and factory utility files in tests/helpers/ or tests/factories/
  • Migration test scripts validating up/down migrations
  • Query performance benchmarks with EXPLAIN ANALYZE output
  • Test database Docker Compose configuration

Error Handling

Error Cause Solution
Foreign key constraint violation during cleanup Truncation order does not respect foreign key dependencies Truncate tables in reverse dependency order; or disable FK checks during cleanup (SET CONSTRAINTS ALL DEFERRED)
Connection pool exhausted Too many test workers opening separate connections Use a single shared connection for tests; limit pool size; close connections in afterAll
Migration fails on test database Schema drift between development and test databases Drop and recreate test database; run all migrations from scratch; verify migration checksums
Transaction rollback does not clean up ORM auto-commits or test creates a new connection outside the transaction Inject the transaction connection into all ORM operations; disable auto-commit in test config
Slow test suite due to database I/O Too many INSERT/DELETE operations per test Use in-memory SQLite for unit tests; batch seed data; use transaction rollback instead of truncation

Examples

Jest with Prisma transaction rollback:

import { PrismaClient } from '@prisma/client';

const prisma = new PrismaClient();

describe('UserRepository', () => {
  afterAll(async () => { await prisma.$disconnect(); });

  it('creates and retrieves a user', async () => {
    await prisma.$transaction(async (tx) => {
      const created = await tx.user.create({
        data: { name: 'Alice', email: 'alice@test.com' },
      });
      const found = await tx.user.findUnique({ where: { id: created.id } });
      expect(found).toMatchObject({ name: 'Alice', email: 'alice@test.com' });
      // Transaction rolls back automatically when we throw
      throw new Error('ROLLBACK');
    }).catch((e) => {
      if (e.message !== 'ROLLBACK') throw e;
    });
  });
});

pytest with database fixture and rollback:

import pytest
from sqlalchemy import create_engine
from sqlalchemy.orm import Session

@pytest.fixture
def db_session():
    engine = create_engine("postgresql://test:test@localhost:5433/testdb")  # 5433 = configured value
    connection = engine.connect()
    transaction = connection.begin()
    session = Session(bind=connection)
    yield session
    session.close()
    transaction.rollback()
    connection.close()

def test_insert_and_query_user(db_session):
    db_session.execute(
        text("INSERT INTO users (name, email) VALUES (:n, :e)"),
        {"n": "Alice", "e": "alice@test.com"}
    )
    result = db_session.execute(text("SELECT name FROM users WHERE email = :e"),
                                 {"e": "alice@test.com"}).fetchone()
    assert result[0] == "Alice"

Migration validation test:

describe('Database Migrations', () => {
  it('applies all migrations to empty database', async () => {
    const result = await exec('npx prisma migrate deploy');
    expect(result.exitCode).toBe(0);
  });

  it('migration is idempotent', async () => {
    await exec('npx prisma migrate deploy');
    const result = await exec('npx prisma migrate deploy');
    expect(result.exitCode).toBe(0); // Second run should succeed (no-op)
  });
});

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides a suite of tools for database testing, including Docker configurations and test data generation scripts. It downloads a utility from the trusted Anthropics GitHub repository. Security considerations include hardcoded credentials in a local-only Docker Compose file and the dynamic generation of shell scripts from templates, which are considered low-risk given the skill's purpose as a development and testing aid.

  • Socket2mo

    1 alert: gptAnomaly

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 3 months ago
What it can do
Reads files Edits files Runs commands
version
1.26.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "testing",
  "database",
  "database-tests"
]
All 6 allowed tools
ReadWriteEditGrepGlobBash(test:db-*)
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/managing-database-tests