When CSV works best
CSV is easy to open in spreadsheets, attach to QA tickets, and review manually. It works well when a tester needs to scan many generated addresses or share a simple fixture list with a non-developer.
For ecommerce checkout testing, CSV can also support import tests, demo store setup, and manual comparison across regions.
When JSON works best
JSON preserves field names and structure, which makes it better for automated tests, frontend fixture files, mocked response data, and developer tooling.
A JSON export is usually easier to load into test runners because each record keeps fields such as fullName, phoneNumber, streetAddress, city, region, postcode, and fullAddress.
Use both for the same saved records
The saved address workflow lets you save generated records locally and export the same saved set as either CSV or JSON. That keeps QA and engineering aligned around the same synthetic input data.
The workflow is simple: generate records, save the useful ones, export the format your team needs, and attach the file to the test plan or issue.
Keep exports organized
Use descriptive filenames and avoid mixing unrelated countries in the same fixture unless the test case requires it.
For example, a postcode formatting test may use UK-only data, while an international checkout test may intentionally combine US, Canada, Singapore, and Hong Kong records.