CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/faker-data

Authors test-data factories using Faker: the Python `faker` library, the `@faker-js/faker` JS port, and the `faker-ruby` gem. Owns the library mechanics end to end: 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 an existing dataset that already holds real records - a production dump in staging goes to pii-masking-pipeline-builder in qa-test-data-privacy (its faker-masking-operators reference), which owns referential integrity and re-identification. Prefer this skill when the codebase already uses the Faker family or when cross-language consistency across Python, JS, and Ruby matters; use synthetic-data-toolkit's mimesis reference only when deeper Python locale coverage is the priority. Use when authoring fixtures or factories that need realistic-looking field values.

89

Quality

89%

Does it follow best practices?

Impact

Average score across 10 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Evaluation results

Failed

Every order in our fixtures belongs to a customer who doesn't exist

Failed

Half of contact.js has no tests because our fixtures can't reach it

Failed

Inventory tests can't be run one at a time

Failed

Nightly run failed on a cart nobody can get back

Failed

Nothing in the suite ever inserts a second account

Failed

Nothing our factory generates gets past the contact API

Failed

Profile suite can't be pointed at the German or Japanese market

Failed

Receipt test can only ever see one customer

Failed

Seed 1337 gives everyone different data

Failed

Staging seeding sent 214 welcome emails to real people

Agent
Claude Code
Model
Claude Sonnet 4.6