Mock Feature Flag Config Generator

How to use

1. 1️⃣
   Choose your options above
2. 2️⃣
   Click Generate
3. 3️⃣
   Copy your result

Detailed instructions

1. Set the Number of Flags input to match how many flag objects your test scenario or UI requires.
2. Select your Output Format — JSON for API mocking, YAML for Kubernetes configs, or ENV for serverless deployments.
3. Click Generate to produce a complete, randomized feature flag configuration object.
4. Copy the output and paste it into your fixture file, seed script, or test setup block.
5. Regenerate as many times as needed to get different rollout percentages and flag states for broader test coverage.

Use Cases

• •Seeding a feature flag admin dashboard with 8+ realistic sample flags for UI development
• •Generating JSON fixture files for Jest unit tests covering partial rollout edge cases
• •Mocking LaunchDarkly or Unleash configs inside Cypress integration test suites
• •Populating a local Flagsmith or Flipt instance with varied flag states during dev setup
• •Creating YAML fixtures for Kubernetes feature flag ConfigMap and Helm chart testing

Tips

• →Generate the same flag count twice and diff the outputs to build test cases that verify your system handles config changes correctly.
• →For ENV format output, pipe it directly into a `.env.test` file — most test runners load this automatically without extra setup.
• →When testing partial rollout logic, look for flags with 1-99% rollout values in the output; these are the edge cases most evaluation bugs hide in.
• →Combine JSON output with a schema validator like Ajv or Zod in your test suite to confirm your flag parser handles every generated shape without errors.
• →Generate 20+ flags when building a flag management UI — you need enough data to trigger pagination, overflow states, and search filtering realistically.
• →For LaunchDarkly SDK mock testing, use the JSON output as the response body in an MSW or nock interceptor to simulate the flag evaluation API.

FAQ