mimesis-data
Authors Python test fixtures using mimesis - a fast, type-hinted, locale-aware test-data generator with 46 locales - covering Person / Address / Internet / Datetime providers and the Schema/Field pattern for typed-dict generation. Pairs with factory_boy when referential integrity is needed. Use when the project is Python and the team values speed, type hints, or strong locale coverage over Faker's larger ecosystem.
Install with skills.sh (any agent)
npx skills add testland/qa --skill mimesis-datamimesis-data
Overview
Mimesis is a Python test-data generator that's "widely recognized as the fastest data generator among Python solutions" with full type hints for editor autocompletion (mimesis-readme (opens in new window)).
The library supports 46 locales (mimesis-readme (opens in new window)) and exposes both per-provider methods (Person.full_name()) and a schema-based generator for typed-dict shapes.
When to use
If the team is already standardized on Faker, switching is rarely worth it - see faker-data. If the team needs factory orchestration with referential integrity, pair mimesis with factory_boy (or use factory-bot-data in Ruby projects).
Install
pip install mimesis(Per mimesis-readme (opens in new window).)
Authoring
Per-provider usage
from mimesis import Person, Address, Internet, Datetime
from mimesis.locales import Locale
person = Person(Locale.EN)
person.full_name() # 'Brande Sears'
person.email(domains=['example.com']) # 'roccelline1878@example.com'
person.gender()
person.title()
address = Address(Locale.EN)
address.full_address() # '123 Main St, Springfield, IL 62701'
address.city()
address.country()
internet = Internet()
internet.url()
internet.ip_v4()
internet.user_agent()
dt = Datetime()
dt.datetime()
dt.date()
dt.formatted_datetime()(Adapted from mimesis-readme (opens in new window).)
Generic - one entry point per locale
from mimesis import Generic
from mimesis.locales import Locale
g = Generic(Locale.EN)
g.person.full_name()
g.address.city()
g.internet.email()Generic aggregates every provider under one instance - preferred when a fixture needs values from multiple providers; avoids constructing one provider per type.
Schema-based - typed-dict generation
from mimesis import Field, Schema, Locale
field = Field(Locale.EN)
# Build one row's worth of data
def schema():
return {
"id": field("uuid"),
"name": field("person.full_name"),
"email": field("person.email"),
"created_at": field("datetime.datetime"),
"address": {
"city": field("address.city"),
"zip": field("address.postal_code"),
},
}
# Generate a list of rows
generator = Schema(schema=schema, iterations=1000)
data = generator.create() # → list of 1000 dicts(Adapted from mimesis-readme (opens in new window) schema documentation.)
The schema/field pattern is mimesis's distinguishing feature - it produces typed-dict shapes without per-field method calls, which makes it convenient for bulk fixture generation (e.g. seeding a test DB with 10k rows).
Locale support
from mimesis import Person
from mimesis.locales import Locale
Person(Locale.EN).full_name() # 'Brande Sears'
Person(Locale.JA).full_name() # '広橋 美月'
Person(Locale.RU).full_name() # 'Анастасия Иванова'
Person(Locale.DE).full_name() # 'Klaus Müller'Per mimesis-readme (opens in new window), 46 locales are supported. Full list at mimesis.name/latest/locales.html (opens in new window).
Seeding for determinism
from mimesis import Generic
from mimesis.locales import Locale
g = Generic(Locale.EN, seed=12345)
g.person.full_name() # deterministic based on seedPass seed= at provider construction; subsequent calls are deterministic. Same as faker-data, seed in tests so failures reproduce locally.
Pairing with factory_boy
Mimesis can be the value engine for factory_boy:
from factory import Factory, LazyFunction
from mimesis import Person, Locale
from myapp.models import User
person = Person(Locale.EN, seed=42)
class UserFactory(Factory):
class Meta:
model = User
name = LazyFunction(person.full_name)
email = LazyFunction(lambda: person.email())LazyFunction ensures each factory instantiation re-calls the mimesis method - getting a new value per fixture, not a single shared one.
Anti-patterns
| Anti-pattern | Why it fails | Fix |
|---|---|---|
| Constructing one provider per attribute | Person() per field is N times the constructor cost; slows bulk generation. | Use Generic once; access providers as attributes. |
Hardcoding seed= literally to a value the test depends on | Brittle: a mimesis update changes the PRNG sequence; the test fails next upgrade. | Pin mimesis version; OR assert patterns (matches a regex), not literal values. |
| Using mimesis for security payloads | Mimesis generates realistic-looking data; SQL injection / XSS won't appear. | Use malicious-payload-bank. |
| Schema with 100k iterations in pytest | Memory-bound; slow. | Generate to disk (Schema.to_csv, Schema.to_json) and seed the DB outside the test. |
| Mixing mimesis + Faker in the same project | Two PRNGs to seed; two doc surfaces; two upgrade cadences. | Pick one; if migrating, do it in a single PR. |
Limitations
References
Related skills
bogus-data
Authors .NET test fixtures using the Bogus library - fluent typed `Faker` builders with `.RuleFor` per property, generation via `Generate()` / `GenerateBetween(min, max)` / `GenerateLazy()`, and `UseSeed()` for reproducibility. Provides the Bogus equivalent of Python's Faker / Ruby's FactoryBot. Use when the project is C# / F# / VB.NET and the team needs typed fixture creation.
boundary-value-generator
Generates boundary-value test cases from typed input specifications - for each input field, produces the canonical 6-point set (one below, at, and above the lower bound; one below, at, and above the upper bound) plus equivalence-class representatives. Emits cases as parameterized test inputs (pytest @parametrize / Jest test.each / xUnit InlineData / etc.). Use when a function or endpoint has numeric / string-length / collection-size constraints and the team needs systematic edge-case coverage.
e2e-test-narrative-builder
Assembles a multi-step end-to-end user-journey test from a list of high-level user intents - translates each intent ("user signs up", "user adds product to cart", "user completes checkout with promo code") into the corresponding test-runner step (Playwright / Cypress / Selenium / Karate), wires shared state across steps via test fixtures, and emits the resulting test as a single Scenario in the project's E2E framework. Use when scaffolding an E2E test that exercises a complete user flow rather than a single page.
factory-bot-data
Authors Ruby FactoryBot factories with traits, associations, sequences, and the three build strategies (build / create / build_stubbed); integrates with RSpec / Minitest test suites; pairs with Faker for randomized field values. Use when the project is Ruby / Rails and needs structured fixture creation with referential integrity.
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, which raises referential-integrity and re-identification concerns this skill does not address. Prefer this skill when the codebase already uses the Faker family or when cross-language consistency across Python, JS, and Ruby matters; use mimesis-data only when deeper Python locale coverage is the primary requirement. Use when authoring fixtures or factories that need realistic-looking field values.
golden-file-conventions
Reference catalog for snapshot / golden file management - naming conventions, directory layout, when to add / update / remove a baseline, sanitization (timestamps, IDs, PII), per-OS / per-runtime variant strategy, and review workflow for snapshot diffs in PRs. Use when designing a snapshot-testing convention or auditing an existing one for drift.
malicious-payload-bank
Reference catalog of curated adversarial input payloads keyed by attack class - SQL injection, XSS, SSRF, path traversal, command injection, XXE, prototype pollution, regex DoS, Unicode confusables, header injection - plus per-context guidance for which payloads apply (URL parameter / form input / JSON body / file upload). Use when authoring negative-test cases for input validation, fuzz targets, or a security-focused test suite that needs to exercise the OWASP Top 10 attack surface.
mountebank-imposters
Authors Mountebank imposters (multi-protocol mock servers - HTTP, HTTPS, TCP, SMTP, LDAP, gRPC, WebSockets, GraphQL, and more) by POSTing JSON definitions to the Mountebank control API on port 2525, configures stubs with predicates and responses, and uses record-playback proxy mode to capture upstream traffic. Use when the project needs a multi-protocol mock server beyond HTTP-only tools like WireMock or MSW.
msw-handlers
Authors Mock Service Worker (MSW) request handlers for both browser and Node.js test environments using the `http.get` / `http.post` / `HttpResponse.json` API, wires them via `setupWorker` (browser) or `setupServer` (Node), and manages the test lifecycle (`server.listen` / `resetHandlers` / `close`). Use when the project uses JavaScript / TypeScript and needs to mock fetch / XHR at the network layer for both Vitest / Jest unit tests and Cypress / Playwright integration tests.
negative-test-generator
Generates negative / error-path test cases that mirror happy-path tests - for each happy-path test, produces companions exercising input validation rejection, missing required fields, type mismatches, authorization failures, rate-limit errors, and adversarial payloads from the malicious-payload-bank. Emits cases as parameterized tests in the project's runner format. Use when a feature has happy-path coverage but the rejection / error / unauthorized paths are untested.
pairwise-test-case-generator
Generates parameterized test inputs combining boundary-value, equivalence-class, and pairwise-combinatorial cases from a typed multi-input specification - produces the cross-product of cases up to a configurable strength (1-wise / 2-wise / N-wise) using all-pairs reduction so the test surface stays tractable. Emits cases in the project's test-runner-native parametrize format. Use when a function or endpoint takes 3+ inputs whose interactions matter and full Cartesian product would explode.
seed-data-curator
Builds a reproducible E2E seed dataset for the project's test environments - picks a representative user / org / data-product cross-section, generates the rows via the project's chosen factory library (FactoryBot / mimesis / Bogus / Faker + factory_boy), persists the dataset as a checked-in fixture (SQL dump / JSON / per-engine seed file), and wires it into the test bootstrap. Use when starting E2E coverage on a project that has no seed strategy, or when an existing seed has drifted.
synthetic-data-tool-selector
Chooses between the four mainstream synthetic test-data generators - Faker (JavaScript), FactoryBot (Ruby), mimesis (Python), Bogus (.NET) - picks the right tool by language and use case (raw value generation vs. typed factory orchestration), shows side-by-side equivalents for the same fixture across all four, and emits the language-appropriate code. Use when starting test-data work on a project and the team wants the "which tool should I use" decision documented.
synthetic-pii-generator
Generates realistic-but-fake personally identifiable information (PII) - emails, phone numbers, SSNs / national IDs, addresses, names, credit-card numbers (test BIN ranges), date-of-birth - for non-production environments. Wraps Faker / mimesis with PII-aware constraints so generated values match real format expectations (Luhn-valid card numbers, region-valid phone formats, ITIN/SSN format) without ever generating real-person data. Use when seeding test environments, building demo data, or replacing real PII in copied datasets.
test-data-patterns
Pure reference catalog of the cross-language object-construction patterns for test data - Test Data Builder (Pryce/Freeman), Factory (with traits and associations), Object Mother, Fixture composition (per-test / per-describe / shared), Snapshot (defers to `golden-file-conventions` for the operational details), and Production-Data Anonymisation. Distinct from per-language data wrappers (`factory-bot-data` Ruby, `faker-data` JS, `mimesis-data` Python, `bogus-data` .NET) which document tool-specific configuration; this catalog is the architecture-tier reference for choosing **which pattern** before reaching for the tool. Use when choosing a test-data construction pattern for a new suite, or auditing an existing suite whose fixtures have drifted into shared mutable state.
wiremock-stubs
Authors WireMock stub mappings for HTTP service mocking - `stubFor` with verb/path/header matchers + `willReturn` response shaping, lifecycle via `WireMockServer` (start / stop) or JUnit `WireMockExtension`, request verification via `verify()`, and dynamic-port allocation for parallel tests. Use when the project is JVM-based and tests need to mock HTTP dependencies (third-party APIs, internal microservices) at the network layer.