qa-test-data
Test data engineering: Faker and factories, WireMock and MSW API mocks, seed datasets, golden files, and boundary, pairwise and negative test inputs. Includes FactoryBot, Mimesis and Bogus, a Mountebank reference, synthetic PII, and a malicious payload bank. Agents (golden-file-manager, test-data-setup-agent) maintain snapshot baselines and set up a feature's full test-data layer.
Install this plugin
View source (opens in a new tab)/plugin install qa-test-data@testland-qaFirst time? Add the marketplace with /plugin marketplace add testland/qa
Plugin
- Category
- Foundations
- Version
v1.4.9- Contents
- 12 skills · 2 agents
Skills12
boundary-value-generatorGenerates 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.skillfaker-dataFixes 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.skillgolden-file-conventionsReference 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.skillmalicious-payload-bankUse when writing negative tests for input validation, fuzz targets or security tests that need real attack strings: SQL injection, XSS, SSRF, path traversal, command injection, XXE, prototype pollution, ReDoS, Unicode confusables and header injection, with which payloads fit each input context.skillmsw-handlersAuthors 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).skillnegative-test-generatorUse when code has deliberate error paths but the tests only prove the success case.skillpairwise-test-case-generatorUse when a function or endpoint takes 3 or more inputs whose combinations matter and the full Cartesian product is too large.skillseed-data-curatorUse when E2E tests need a reproducible seed dataset and the project has none, or the existing seed has drifted.skillsynthetic-data-toolkitUse whenever someone asks for test factories or a FactoryBot setup, even a quick one: factories with traits and associations (Ruby, Rails), Mimesis bulk data (Python), Bogus Faker<T> builders (.NET), or which generator fits.skillsynthetic-pii-generatorUse when seeding non-production environments, building demo data, or replacing real personal data in copied datasets.skilltest-data-patternsUse when choosing how a test suite builds its test data, or when fixtures have drifted into shared mutable state.skillwiremock-stubsUse whenever Java/JVM tests call a slow, flaky, rate-limited or paid HTTP API: stub it with WireMock so tests run offline, including faults such as timeouts and 500 responses, request verification and parallel-safe ports.skill
Agents2
golden-file-managerAction-taking agent that maintains snapshot / golden file health across a project - adds new baselines for previously-uncovered tests, updates baselines after intentional changes (refusing to update if the diff doesn't match the PR's stated intent), prunes orphaned baselines whose tests no longer exist, and applies sanitization rules from the golden-file-conventions catalog.agenttest-data-setup-agentAction-taking agent that sets up a complete test-data layer for a single feature - detects the project language and stack, generates per-test fixture factories (via faker-data or synthetic-data-toolkit), and builds a reproducible E2E seed dataset (via seed-data-curator), wiring both into the test bootstrap.agent
About qa-test-data
Test data engineering: Faker as the default generator plus the synthetic-data-toolkit umbrella (FactoryBot / mimesis / Bogus); WireMock (with Mountebank multi-protocol reference) and MSW mock servers; golden-file conventions + manager; seed-data curator; parameterized / boundary / negative test case generators; synthetic PII; malicious payload bank.
Choosing WireMock vs MSW vs Mountebank
| Project shape | Mock server |
|---|---|
| JVM (Java / Kotlin / Scala), HTTP dependencies | wiremock-stubs - in-process @WireMockTest, typed DSL |
| JS / TS (browser or Node), HTTP dependencies | msw-handlers - one handler set shared across Vitest / Jest / Cypress / Playwright |
| Any stack with non-HTTP dependencies (TCP, SMTP, LDAP, gRPC, WebSockets) | Mountebank - see wiremock-stubs references/mountebank.md |
Pick one per project; add Mountebank only when a dependency genuinely isn't HTTP.