Use case · Migration and data quality

Test data that is realistic, reproducible and not real.

Test Data builds synthetic rows from rules you set, one file per table, in the layout of a file template. Nothing is read from a database.

The problem

Testing an ERP or a conference room pilot needs realistic data, and copying production puts real customers in a test system. Hand-made data is thin and never the same twice.

What you need

Modules. Free baseline up to 1,000 rows per run. Transfer raises it to 100,000.

Edition. DataBridge Server.

Pricing and what each edition includes.

Steps

How DataBridge does it.

Each step names the feature as it appears in the product.

  1. Step 1

    Data set

    A data set is a seed plus one or more tables. Each table becomes one file.

  2. Step 2

    Field rules

    Each field gets a rule: a sequence, number range, date range, weighted list, pattern mask, pool of names or addresses, copy of an earlier column or a reference to a parent table's key.

  3. Step 3

    File template

    Pick a file template as the output layout and the file has exactly that template's columns, in order.

  4. Step 4

    Preview and Generate

    Preview shows the first 50 rows and writes nothing. Generate downloads a zip with one file per table as CSV, TSV, JSON, JSON Lines, XML or Excel.

  5. Step 5

    Repeat

    The same seed and rules always produce byte-identical files, so every test round starts from the same data.

Honest limits

What this does not do.

  • Names, companies and addresses are built in and not real people. The data is for testing, not for analysis.
  • Generating data does not load it. Load the files through your test system's import.
Keep reading

Related pages.

Next step

Try the parts that are free today.

The free browser edition needs no sign-in and never uploads your files.