Runnable test data examples, synthetic data only

Every example lives in the repository with a README, the profile it needs, the commands to run, expected output and cleanup. All data is synthetic.

By sector

  • Healthcare

    Patients and appointments with relationships preserved; masking policy pinned; synthetic values only.

  • Banking

    Insufficient funds, duplicate transactions and chargebacks with account isolation.

  • Insurance

    Policies, claims, payouts and fraud edge cases for regression suites.

  • Retail & e-commerce

    Orders, payments, refunds and inventory with relationship closure.

  • SaaS

    Tenant-isolation regression data for multi-tenant applications.

  • Manufacturing

    Bills of materials, work orders and defect traceability.

  • Database migrations

    Schema evolution tests against an isolated, certified copy per pull request.

Start here

The canonical end-to-end scenario: a healthcare profile on a synthetic PostgreSQL estate, validated, planned, requested, tested and released.

  • Healthcare on PostgreSQL — patients and appointments with relationships preserved, masking pinned, lease released afterwards. examples/test-data-api/scenarios/01-healthcare-postgresql
  • The profile it uses — a TestDataProfile manifest you can validate locally. examples/test-data-api/profiles/healthcare-integration.yaml
  • The whole gallery — scenarios by sector and edge case, each with a README, expected output and cleanup. examples/test-data-api

CI/CD recipes

Thin wrappers over the CLI: authenticate, request, wait, run tests, always release. Illustrative unless marked otherwise.

  • GitHub Actions — Examples in the repository; workload identity requires enablement. examples/integrations/github-actions
  • GitLab CI — Examples in the repository; workload identity requires enablement. examples/integrations/gitlab-ci
  • Jenkins — Compatible via the standard API/CLI — illustrative example. examples/integrations/jenkins
  • Azure DevOps — Compatible via the standard API/CLI — illustrative example. examples/integrations/azure-devops
  • CircleCI — Compatible via the standard API/CLI — illustrative example. examples/integrations/circleci
  • Generic shell (curl / CLI) — Compatible via the standard API/CLI — illustrative example. examples/integrations/generic-shell
  • Blacksmith — GitHub Actions-compatible runner example, illustrative; no partnership. examples/integrations/blacksmith
  • Self-hosted runners and ephemeral Kubernetes — Illustrative examples; the runner must reach the approved target. examples/integrations/self-hosted-runner

AI agents (Preview)

A local stdio MCP adapter that exposes bounded, metadata-only tools and calls the same API with your own session.

  • Local MCP adapter — list permitted profiles, validate, plan, request, poll, evidence and release; permission-denied and needs-approval flows. examples/mcp

Try it without your own data

The synthetic playground runs the TDM workflow in your browser. The examples above run against a local, synthetic control plane and agent where noted.

Build with Test Data API