mcpField
Q
qe-database-testing

qe-database-testing

github.com/proffesor-for-testingTesting & quality51982 installsUpdated today
Repository

About qe-database-testing

qe-database-testing is a database testing skill with checks and examples for schema, data integrity, migrations, transactions, and query performance. It is for developers and testers, with particular attention to reversible migrations and concurrent transaction behavior.

Key features

  1. 01Validate tables, columns, and constraints
  2. 02Check uniqueness, foreign keys, and data integrity
  3. 03Test migration execution and rollback
  4. 04Verify transaction isolation and ACID properties
  5. 05Measure query performance and index use

Use cases

  1. 01Validate a new table or database schema
  2. 02Check that migrations roll back while preserving data
  3. 03Test transaction rollback after an error
  4. 04Investigate query performance issues

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill qe-database-testing

After installing, type/qe-database-testingin Claude Code to confirm it loaded.

Details

From the project README

Database Testing

<default_to_action> When testing database operations:

  1. VALIDATE schema (tables, columns, constraints exist as expected)
  2. TEST data integrity (unique, foreign key, check constraints)
  3. VERIFY migrations (forward works, rollback works, data preserved)
  4. CHECK transaction isolation (ACID properties, concurrent access)
  5. MEASURE query performance (indexes used, execution time)

Quick DB Testing Checklist:

  • Schema matches specification
  • Unique constraints prevent duplicates
  • Foreign keys prevent orphaned records
  • Migrations are reversible
  • Transactions roll back on error

Critical Success Factors:

  • Database bugs cause data loss/corruption (catastrophic)
  • Test migrations in staging before production
  • Transaction tests catch concurrency bugs </default_to_action>

Quick Reference Card

When to Use
  • New table/schema creation
  • Migration development
  • Data integrity validation
  • Query performance optimization
Database Test Types
TypeFocusWhen
SchemaStructure correctTable creation
IntegrityConstraints workData operations
MigrationUp/down workSchema changes
TransactionACID propertiesConcurrent access
PerformanceQuery speedOptimization
ACID Properties
PropertyTest Focus
AtomicityAll or nothing (rollback on error)
ConsistencyConstraints always valid
IsolationConcurrent transactions don't interfere
DurabilityCommitted data persists

Schema Testing

test('users table has correct schema', async () => {
  const schema = await db.raw(`
    SELECT column_name, data_type, is_nullable
    FROM information_schema.columns
    WHERE table_name = 'users'
  `);

  expect(schema).toContainEqual({
    column_name: 'id',
    data_type: 'integer',
    is_nullable: 'NO'
  });

  expect(schema).toContainEqual({
    column_name: 'email',
    data_type: 'character varying',
    is_nullable: 'NO'
  });
});

Data Integrity Testing

test('email must be unique', async () => {
  await db.users.create({ email: '[email protected]' });

  await expect(
    db.users.create({ email: '[email protected]' })
  ).rejects.toThrow('unique constraint violation');
});

test('foreign key prevents orphaned records', async () => {
  const user = await db.users.create({ email: '[email protected]' });
  await db.orders.create({ userId: user.id, total: 100 });

  await expect(
    db.users.delete({ id: user.id })
  ).rejects.toThrow('foreign key constraint');
});

Migration Testing

test('migration is reversible', async () => {
  await migrate('add-users-table');

  // Table exists after migration
  const tables = await db.raw(`SELECT table_name FROM information_schema.tables`);
  expect(tables.map(t => t.table_name)).toContain('users');

  await rollback('add-users-table');

  // Table gone after rollback
  const tablesAfter = await db.raw(`SELECT table_name FROM information_schema.tables`);
  expect(tablesAfter.map(t => t.table_name)).not.toContain('users');
});

test('migration preserves existing data', async () => {
  await db.users.create({ email: '[email protected]' });

  await migrate('add-age-column');

  const user = await db.users.findOne({ email: '[email protected]' });
  expect(user).toBeDefined();
  expect(user.age).toBeNull(); // New column, null default
});

Transaction Testing

test('transaction rolls back on error', async () => {
  const initialCount = await db.users.count();

  try {
    await db.transaction(async (trx) => {
      await trx('users').insert({ email: '[email protected]' });
      await trx('users').insert({ email: '[email protected]' });
      throw new Error('Rollback test');
    });
  } catch (error) { /* Expected */ }

  expect(await db.users.count()).toBe(initialCount);
});

test('concurrent transactions isolated', async () => {
  const user = await db.users.create({ balance: 100 });

  // Two concurrent withdrawals (race condition test)
  await Promise.all([
    db.transaction(async (trx) => {
      const current = await trx('users').where({ id: user.id }).first();
      await trx('users').update({ balance: current.balance - 50 });
    }),
    db.transaction(async (trx) => {
      const current = await trx('users').where({ id: user.id }).first();
      await trx('users').update({ balance: current.balance - 50 });
    })
  ]);

  const final = await db.users.findOne({ id: user.id });
  expect(final.balance).toBe(0); // Proper isolation
});

Agent-Driven Database Testing

// Generate test data with integrity
await Task("Generate Test Data", {
  schema: 'ecommerce',
  tables: ['users', 'products', 'orders'],
  count: { users: 1000, products: 500, orders: 5000 },
  preserveReferentialIntegrity: true
}, "qe-test-data-architect");

// Test migration safety
await Task("Migration Test", {
  migration: 'add-payment-status-column',
  tests: ['forward', 'rollback', 'data-preservation'],
  environment: 'staging'
}, "qe-test-executor");

Agent Coordination Hints

Memory Namespace
aqe/database-testing/
├── schema-snapshots/*   - Current schema state
├── migrations/*         - Migration test results
├── integrity/*          - Constraint validation
└── performance/*        - Query benchmarks
Fleet Coordination
const dbFleet = await FleetManager.coordinate({
  strategy: 'database-testing',
  agents: [
    'qe-test-data-architect',  // Generate test data
    'qe-test-executor',        // Run DB tests
    'qe-performance-tester'    // Query performance
  ],
  topology: 'sequential'
});

Related Skills


Remember

Database bugs are catastrophic. Data loss is unrecoverable. Corruption spreads silently. Performance issues compound.

Test migrations before production: Forward works, rollback works, data preserved, performance acceptable. Never deploy untested migrations.

With Agents: qe-test-data-architect generates realistic test data with referential integrity. qe-test-executor validates migrations automatically in CI/CD.

Comments

Markdown supported