Skip to content
cccskills
FreePublished on GitHub

faker-data

Fixes test data that breaks tests - factory values in a shape the code under test rejects (a phone number that is not E.164), fixtures that only pass when the whole suite runs in order, and random values that make an assertion pass or fail depending on the run. Authors test-data factories with Faker: the Python `faker` library, the `@faker-js/faker` JS port, and the `faker-ruby` gem - install per language, the provider catalogue (person / internet / location / date / finance / lorem), locale selection and multi-locale mode, and seed-based determinism for reproducible runs. Scope is generating fresh values for tests that start from nothing, not replacing values inside a dataset that already holds real records - that goes to pii-masking-pipeline-builder. Use when fixtures need realistic values, a stable shape, or a fixed seed.

The English summary is being prepared. Showing the original description.

testland/qa13 stars(GitHub 13 + cccskills 0)

Run score Not tested

See how to install

Files included (22)

  • SKILL.md8.7 KB
  • .tessl-plugin/plugin.json963 B
  • evals/ci-failure-cannot-be-reproduced/criteria.json4.5 KB
  • evals/ci-failure-cannot-be-reproduced/task.md3.6 KB
  • evals/every-account-is-john-doe/criteria.json4.3 KB
  • evals/every-account-is-john-doe/task.md3.5 KB
  • evals/fixture-data-shifts-when-a-test-is-added/criteria.json3.9 KB
  • evals/fixture-data-shifts-when-a-test-is-added/task.md3.9 KB
  • evals/fixture-values-do-not-resemble-the-domain/criteria.json4.3 KB
  • evals/fixture-values-do-not-resemble-the-domain/task.md4.2 KB
  • evals/generated-phone-numbers-rejected-by-api/criteria.json4.4 KB
  • evals/generated-phone-numbers-rejected-by-api/task.md3.6 KB
  • evals/orders-reference-users-that-never-existed/criteria.json4.0 KB
  • evals/orders-reference-users-that-never-existed/task.md4.0 KB
  • evals/profile-suite-breaks-outside-en-us/criteria.json4.4 KB
  • evals/profile-suite-breaks-outside-en-us/task.md3.4 KB
  • evals/receipt-test-compares-against-pasted-output/criteria.json4.1 KB
  • evals/receipt-test-compares-against-pasted-output/task.md3.2 KB
  • evals/same-seed-different-data-per-machine/criteria.json4.1 KB
  • evals/same-seed-different-data-per-machine/task.md3.2 KB
  • evals/staging-emails-reach-real-mailboxes/criteria.json4.0 KB
  • evals/staging-emails-reach-real-mailboxes/task.md4.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

faker-data

Overview

Faker is a family of libraries (Python / JS / Ruby / Java / .NET / PHP) that generate realistic synthetic field values - names, emails, addresses, dates, etc. - for test fixtures. The three most common ports in this skill's scope:

LanguageLibraryReference
Pythonfakerfaker-py
JS / TS@faker-js/fakerfaker-js
Rubyfaker-ruby/fakerfaker-rb

For .NET (Bogus) and Python-specifically with stronger locale coverage (mimesis), see synthetic-data-toolkit.

When to use

  • A test fixture needs realistic but synthetic field values (the default 'foo' / 'bar' pattern produces tests that miss real bugs around long names, Unicode, edge-case formats).
  • The team wants reproducible randomness - same seed produces same data, useful for regression repro.
  • Locale coverage matters (i18n testing across de_DE, ja_JP, ar_SA, etc.).
  • A factory library (FactoryBot, factory_boy, Bogus) needs the underlying generator - Faker is typically the random-data engine plugged into those.

Install

Python

pip install Faker

(Per faker-py.)

JavaScript / TypeScript

npm install --save-dev @faker-js/faker

(Per faker-js.)

Ruby

# Gemfile
gem 'faker', group: :test

(Per faker-rb.)

Authoring

Python

from faker import Faker

fake = Faker()
fake.name()              # 'Margaret Boehm'
fake.email()             # 'walker.travis@example.com'
fake.address()           # '123 Main St, Apt 4B\nSpringfield, IL 62701'
fake.phone_number()      # '+1-555-867-5309'
fake.date_of_birth(minimum_age=18, maximum_age=65)
fake.text(max_nb_chars=200)

(Per faker-py.)

Common provider modules: person (name, prefix), address, internet (email, url, ipv4), phone_number, date_time, lorem (paragraphs, sentences, words), company, credit_card, job (faker-py).

JavaScript

import { faker } from '@faker-js/faker';

faker.person.fullName();           // 'Margaret Boehm'
faker.internet.email();             // 'walker.travis@example.com'
faker.location.streetAddress();     // '123 Main St'
faker.phone.number();               // '+1-555-867-5309'
faker.date.past({ years: 30 });
faker.lorem.paragraphs(2);

(Per faker-js.)

Module organization mirrors the Python ports but uses the module- namespace form: faker.person.*, faker.internet.*, faker.location.*, faker.date.*, faker.finance.*, faker.commerce.* (faker-js).

Ruby

require 'faker'

Faker::Name.name           # 'Margaret Boehm'
Faker::Internet.email      # 'walker.travis@example.com'
Faker::Address.full_address
Faker::PhoneNumber.cell_phone
Faker::Date.birthday(min_age: 18, max_age: 65)
Faker::Lorem.paragraphs(number: 2)

(Per faker-rb.)

Seeding for deterministic output

The most common test-stability mistake is letting Faker generate non-deterministic values across runs. Always seed in tests so a failure can be reproduced.

Python

from faker import Faker

# Class-level - sets the default RNG for all subsequent Faker() calls
Faker.seed(4321)
fake = Faker()

# Instance-level - useful when multiple Faker instances need different seeds
fake.seed_instance(4321)

(Per faker-py.)

JavaScript

import { faker } from '@faker-js/faker';

faker.seed(123);
// All faker.* calls until the next seed() are deterministic.

(Per faker-js.)

Ruby

require 'faker'

Faker::Config.random = Random.new(42)

For test frameworks: place the seed in beforeEach / setup so each test starts with the same baseline; for paired runs, persist the seed used per failing test (similar to the flake-pattern-reference Pattern 8 randomness guidance).

Locale support

Python

fake = Faker('it_IT')                # Italian
fake = Faker(['en_US', 'fr_FR', 'ja_JP'])   # Multi-locale (random per call)
fake.name()                          # generates per the configured locale(s)

(Per faker-py.)

JavaScript

import { fakerDE } from '@faker-js/faker';
import { fakerJA } from '@faker-js/faker';

fakerDE.person.fullName();   // German name
fakerJA.address.city();       // Japanese city

(Per faker-js; 70+ locales available.)

Ruby

Faker::Config.locale = :ja
Faker::Name.name   # Japanese name

(Per faker-rb.)

Composing factories with referential integrity

Faker generates field values; for referential integrity (a factory that creates a User with a related Order), use a factory library that wraps Faker:

LanguageFactory librarySkill
Pythonfactory_boy(consider mimesis - synthetic-data-toolkit - for locale-rich generation)
JS / TSfishery / factory.tshand-rolled with Faker as engine
RubyFactoryBotsynthetic-data-toolkit references/factory-bot.md
.NETBogussynthetic-data-toolkit references/bogus.md

Faker alone won't enforce that order.user_id == user.id; the factory library handles that.

Anti-patterns

Anti-patternWhy it failsFix
Calling Faker without a seed in testsA failure on CI doesn't reproduce locally; flake-investigation guesswork.Seed once per test or per suite (Faker.seed(...)).
Using fake.email() with a real domain (example.com is shared)Spam concerns; some validators reject example.com.Faker's defaults use safe RFC-2606 domains; never override to a real domain in tests.
Hardcoding generated values into snapshotsSnapshot bound to a Faker version's PRNG sequence; library bump breaks the snapshot.Snapshot the shape of the data; assert types and patterns rather than literal values.
Generating names with the wrong localeA test asserting "name has at least one space" fails on :ja (Japanese) where names use ・.Match the locale to the assertion; or relax the assertion to be locale-aware.
Using Faker for security testing payloadsFaker generates "realistic" data, not malicious. SQL injection / XSS won't happen by chance.Use malicious-payload-bank for adversarial input.

Limitations

  • PRNG sequence varies across major versions. A seed produces different values in Faker v18 vs v19. Pin the version in CI for deterministic tests.
  • Locale coverage is uneven. en_US is the most complete; less- common locales fall back to defaults silently. Test the locales you care about; don't assume completeness.
  • Realistic ≠ valid. Faker may generate an email with a technically-valid but unusual format (e.g. +-tagged); your validation may reject it. Match Faker's domain provider to your validator's regex.

References

  • faker-py - Python Faker docs (install, seed, locale, providers).
  • faker-js - @faker-js/faker (modules, seed, 70+ locales).
  • faker-rb - faker-ruby/faker (modules, seed, locale).
  • synthetic-data-toolkit - umbrella dispatcher for the generators beyond plain Faker: mimesis (Python), FactoryBot (Ruby), and Bogus (.NET) workflows in its references/.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Builds a CI gate that fails the build on **new** WCAG / a11y violations introduced by a PR while grandfathering pre-existing violations on a per-rule / per-page baseline. Aggregates verdicts from axe-core / pa11y / Lighthouse a11y / WAVE / IBM Equal Access scans. Use when a project has accumulated a11y debt and a strict "zero violations" gate would block every PR - the ratchet pattern lets the team ship while preventing regressions.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

Workflow skill that builds an A/B-test validity checklist from an experiment proposal, walking the canonical design-correctness gates - pre-registered OEC/power/guardrails, randomization unit + SRM check, assignment integrity, telemetry, peeking discipline, novelty/primacy, post-experiment SRM re-check - into a per-experiment checklist + sign-off form. Use when launching, auditing, or governing an experiment. For pitfall mechanics (guardrails, peeking) see experiment-results-interpreter's references; to read an already-valid result use experiment-results-interpreter; for per-SDK harness tests use experiment-sdk-testing - this gates DESIGN, not SDK code.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

The single install-flow skill: the reference contract for the PWA install flow (installability gate fields, `beforeinstallprompt` handshake, per-platform paths - Android WebAPK / iOS Share menu / Firefox no-op - and the `display-mode` post-install signal, in references/install-flow-reference.md) plus the build-an-X workflow that emits the Add-to-Home-Screen suite. Walks the four-stage timeline, emitting one test per gate cell per [web.dev/articles/install-criteria][install-criteria], the deferred-prompt → `prompt()` → `userChoice` chain per [web.dev/articles/customize-install][customize-install], the iOS Safari manual-metadata branch (`apple-touch-icon`) per [web.dev/learn/pwa/installation][learn-pwa], and the post-install `(display-mode: standalone)` MQ assertion. Output: a Playwright spec with per-stage cells plus a coverage matrix. Use when a PWA's manifest, icons, or install handler change, when install conversion drops at an unknown stage, or when triaging a flaky install assertion.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

Build-an-X workflow that uses an LLM to map existing tests to spec sections - given a spec doc + the test suite, the LLM identifies which tests cover which sections, surfaces uncovered sections (gap), and recommends specific tests to add. Output is a coverage matrix per spec ID. Scope is mapping tests that already exist and naming the gaps, not authoring tests for new acceptance criteria. Use when a spec doc and a test suite both exist but nobody can say which requirements are actually covered - before a release sign-off, an audit, or a decision about where to spend the next round of test effort.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

Generates tests from natural-language specs (acceptance criteria, user stories, requirements) using an LLM, with confidence scoring per test case (LLM self-assessment plus heuristics: assertion quality, naming, completeness), batching uncertain cases for human review, and integration with the team's existing test framework. Use when the user asks to generate unit tests from acceptance criteria, convert user stories to test cases, automate test creation from requirements, or augment a spec-driven test suite with AI-generated stubs that are then curated before merge.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

Configures Allure Report (test-runner adapter install, `allure-results` directory wiring, `categories.json` for failure classification, `history-trend.json` retention via the copy-history-between-runs pattern), runs the Allure CLI to convert `allure-results` to a static HTML site, and uploads the report as a CI artifact. Use when the team needs richer test reporting than JUnit XML - step-level attachments, per-test history, retry tracking, and severity / epic / feature labeling across framework-agnostic adapters (pytest, Jest, JUnit, TestNG, NUnit, Mocha). As a rich static HTML report generator, it is the open-source alternative to the sunset ExtentReports (JVM/.NET per-test HTML narrative); for hosted cross-run flakiness analytics rather than a static per-run report use currents-integration.

The English summary is being prepared. Showing the original description.

testland/qa13Updated Oct 20, 2026

See all skills by testland

Report a problem with this skill