Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Test Data Generation

  • 445 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

test-data-generation is an AI prompt skill that creates realistic synthetic datasets for unit, integration, and QA runs for developers blocked by thin fixtures, privacy rules, or missing edge-case diversity.

About

test-data-generation is a skill from aj-geddes/useful-ai-prompts that produces realistic synthetic datasets when production copies are unavailable or non-compliant. It covers unit, integration, and QA scenarios where fixtures are too thin, privacy policies block real records, or edge cases need diverse data at scale. The skill guides schema-aware generation—valid formats, boundary values, relational consistency, and volume profiles—so tests exercise realistic paths without leaking PII. Reach for test-data-generation when bootstrapping a new service schema, expanding coverage for rare states, or unblocking CI that currently mocks only happy-path rows. Output includes seed files, factory definitions, or bulk JSON/CSV artifacts teams can wire into test runners and staging environments.

  • Realistic synthetic records
  • Edge-case and boundary coverage
  • Privacy-safe alternatives to prod dumps
  • Seeding for integration suites
  • Scalable volume generation

Test Data Generation by the numbers

  • 445 all-time installs (skills.sh)
  • Ranked #630 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill test-data-generation

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs445
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you generate realistic test data without prod copies?

Create realistic synthetic datasets for unit, integration, and QA runs when fixtures are thin, privacy blocks prod copies, or edge cases need diverse records at scale.

Who is it for?

Developers blocked by privacy rules or thin fixtures who need diverse, schema-valid synthetic records at unit, integration, or QA scale.

Skip if: Developers who already have sufficient anonymized production snapshots and only need one trivial mock object.

When should I use this skill?

Test suites lack realistic fixtures, privacy blocks prod data copies, or edge-case diversity is required before running integration or QA pipelines.

What you get

Synthetic datasets, factory definitions, and seed files with diverse edge cases for test suites.

  • Synthetic test datasets
  • Factory or seed file definitions

Files

SKILL.mdMarkdownGitHub ↗

Test Data Generation

Table of Contents

Overview

Test data generation creates realistic, consistent, and maintainable test data for automated testing. Well-designed test data reduces test brittleness, improves readability, and makes it easier to create diverse test scenarios.

When to Use

  • Creating fixtures for integration tests
  • Generating fake data for development databases
  • Building test data with complex relationships
  • Creating realistic user inputs for testing
  • Seeding test databases
  • Generating edge cases and boundary values
  • Building reusable test data factories

Quick Start

Minimal working example:

// tests/factories/userFactory.js
const { faker } = require("@faker-js/faker");

class UserFactory {
  static build(overrides = {}) {
    return {
      id: faker.string.uuid(),
      email: faker.internet.email(),
      firstName: faker.person.firstName(),
      lastName: faker.person.lastName(),
      age: faker.number.int({ min: 18, max: 80 }),
      phone: faker.phone.number(),
      address: {
        street: faker.location.streetAddress(),
        city: faker.location.city(),
        state: faker.location.state(),
        zip: faker.location.zipCode(),
        country: "USA",
      },
      role: "user",
      isActive: true,
      createdAt: faker.date.past(),
      ...overrides,
    };
  }
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Factory Pattern for Test DataFactory Pattern for Test Data
Builder Pattern for Complex ObjectsBuilder Pattern for Complex Objects
Fixtures for Integration TestsFixtures for Integration Tests
Realistic Data GenerationRealistic Data Generation

Best Practices

✅ DO

  • Use faker libraries for realistic data
  • Create reusable factories for common objects
  • Make factories flexible with overrides
  • Generate unique values where needed (emails, IDs)
  • Use builders for complex object construction
  • Create fixtures for integration test setup
  • Generate edge cases (empty strings, nulls, boundaries)
  • Keep test data deterministic when possible

❌ DON'T

  • Hardcode test data in multiple places
  • Use production data in tests
  • Generate truly random data for reproducible tests
  • Create overly complex factory hierarchies
  • Ignore data relationships and constraints
  • Generate massive datasets for simple tests
  • Forget to clean up generated data
  • Use the same test data for all tests

Related skills

How it compares

Pick test-data-generation over test-automation-framework when the blocker is dataset realism and privacy-safe fixtures rather than overall suite architecture.

FAQ

When should developers use test-data-generation?

test-data-generation fits when fixtures are thin, privacy blocks production copies, or edge cases need diverse records at scale. The skill targets unit, integration, and QA tiers with schema-valid synthetic output instead of copying real user data.

What artifacts does test-data-generation produce?

test-data-generation yields synthetic datasets, factory definitions, and seed files—often JSON or CSV—with boundary values and relational consistency. Teams wire these into test runners, staging databases, or CI jobs without exposing production PII.

Testing & QAtestingbackend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.