Skip to generator
fakeloc
Saved addresses

Address test data: fixtures, exports, and repeatable checks

Plan address fixtures around the behavior under test, preserve them in exports, and make failures repeatable.

Separate formatting tests from address verification

A form component can be tested with synthetic values. A shipping integration needs the provider sandbox or an authorized destination. Decide which boundary the test covers before choosing its data.

Keep fixtures small and versioned

Store only the fields the scenario needs, use a stable seed where available, and record the fixture or generator version. When a catalog changes, the version helps explain why a formerly passing snapshot differs.

Turn cases into a checkout matrix

Cover required and optional fields, long values, non-Latin scripts, omitted postal codes, and export/import paths. Keep one expected result per case so a failure points to a specific rule.

Resources

Address test data: fixtures, exports, and repeatable checks

All field notes
Aa →fakeloc / Guides
TEST DATA

Synthetic or deliverable? Know your test data.

Choose address fixtures that fit your test without copying customer information into development.

Read the guide
{ … }fakeloc / Guides
PRIVACY

Better privacy starts with better test fixtures

Make product demos and development environments useful without bringing customer addresses along.

Read the guide
〒fakeloc / Guides
TEST DATA

Reproducible address API fixtures with seeds and versions

Record the parameters that make an API fixture repeatable and know when a catalog update can change it.

Read the guide
Aa →fakeloc / Guides
TEST DATA

A checkout address test matrix for real form behavior

Build a small matrix for field requirements, localization, and recoverable validation errors.

Read the guide