JSON comparison
If timestamps or array order create noise, set comparison rules that match your test objective first.
Compare JSON →- No account or installation
- Copy or download results
- Documents processed in your browser
File sizes and generation counts have limits. Check the limits shown in each tool.
Start with a noisy response
{"updatedAt":"2026-09-21T01:00:00Z","items":[{"id":1,"status":"ready"},{"id":2,"status":"done"}]}On the next response, updatedAt may change and items may arrive in a different order. Neither change necessarily means the business data changed.
Set comparison rules
- Paste the expected and actual JSON into Compare JSON.
- Expand Comparison options and add $.updatedAt as an ignored path.
- Set the identity field to id if every array item has a unique ID.
- Compare. A status change for the same ID should still appear.
Do not hide a real defect
Only ignore fields that the test explicitly treats as irrelevant. Do not ignore a payment amount or final state just to make the results match. Missing IDs and duplicate IDs are reported as errors rather than silently matched.
Current limits
The identity field applies to all arrays. Different IDs per array and wildcard ignored paths are not supported. Null and absent fields remain distinct. Copy only sanitized test responses; never paste production tokens or personal information.