testing

Select PostgreSQL testing methods for core and contrib patches.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/matejformanek/postgres-claude --skill testing-matejformanek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/matejformanek/postgres-claude/tree/main/.claude/skills/testing
Command: npx skills add https://github.com/matejformanek/postgres-claude --skill testing-matejformanek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the ambiguity of choosing the correct PostgreSQL testing framework, ensuring that patches are verified using the appropriate isolation, TAP, or regression methods to prevent buildfarm failures.

Core Features & Use Cases

  • Decision Framework: Provides a clear logic path to select between isolation specs, TAP tests, C-level test modules, or standard regression tests.
  • Integration Guidance: Details exactly which schedule files or meson.build configurations must be updated to wire in new tests.
  • Use Case: When adding a new feature to the PostgreSQL core, use this skill to determine if your test requires a multi-session isolation spec or a standard regression test, and follow the provided steps to ensure it is correctly integrated into the build system.

Quick Start

Use the testing skill to determine the correct test flavor for your current PostgreSQL patch and generate the necessary integration steps.

Frequently Asked Questions about testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between isolation specs, TAP tests, and regression tests for a PostgreSQL core patch?

Choosing the right PostgreSQL testing methodology requires evaluating concurrency, infrastructure, and API requirements to select isolation specs, TAP tests, or regression suites. This decision framework prevents buildfarm failures by matching test flavor to patch complexity.

When do I need to use isolation specs instead of standard regression tests in PostgreSQL?

You need PostgreSQL isolation specs when your test requires multi-session concurrency validation that standard regression tests cannot handle. This framework determines if your patch needs isolation specifications based on concurrency requirements and infrastructure dependencies.

How do I integrate new PostgreSQL tests into meson and parallel_schedule?

Integrating PostgreSQL tests requires updating specific schedule files and meson.build configurations to wire in new isolation, TAP, or regression tests. This ensures stable, reproducible test coverage that integrates seamlessly with the build system.

Does this PostgreSQL testing approach support C-level test modules?

Yes, the PostgreSQL testing framework supports C-level test modules alongside isolation specs and TAP tests. The decision logic evaluates API requirements to determine whether your patch needs C-level modules or standard regression tests.

What's the best way to ensure stable and reproducible PostgreSQL test coverage?

The best way to ensure stable PostgreSQL test coverage is selecting the correct testing methodology—isolation, TAP, or regression—and properly integrating it into meson and parallel_schedule. This prevents buildfarm failures and guarantees reproducible results.