Mock Redis Key-Value Generator

How to use

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

Detailed instructions

1. Enter your application's key namespace (e.g. 'auth', 'cart') in the Key Namespace field.
2. Set the Number of Entries to match how many Redis records your test scenario requires.
3. Click Generate to produce a list of Redis SET commands with namespaced keys and values.
4. Copy the output and paste it into redis-cli, a Docker exec command, or your test seed script.
5. Re-generate as many times as needed to get varied data sets for different test cases.

Use Cases

• •Seeding a local Redis instance before running integration tests in Jest or Pytest
• •Populating a demo Redis environment for stakeholder walkthroughs without copying production data
• •Testing TTL expiry logic with a mix of EX-flagged and persistent entries in a caching layer
• •Validating key namespace isolation between microservices using namespace:type:id patterns
• •Generating beforeEach fixture data for a Redis session-store in a Cypress end-to-end suite

Tips

• →Use a namespace that matches your app's actual prefix so tests catch real key-collision bugs, not artificial ones.
• →Mix multiple generator runs with different namespaces (e.g. 'session' and 'ratelimit') to test cross-namespace isolation logic.
• →When pasting into redis-cli, use the --pipe flag for bulk loading rather than running each command separately — much faster.
• →Save a generated batch to a .redis fixture file and commit it to version control so integration tests are reproducible across environments.
• →Check the TTL values in the output — entries with short EX values are useful for testing expiry-triggered code paths without waiting in real time.
• →If your app uses Redis keyspace notifications, seed with this data and enable notify-keyspace-events to watch expiry events fire during tests.

FAQ