How to validate json changes before and after deployment
- Step 1Capture pre-deployment state — Before deploying, capture the JSON state you will compare post-deployment: the API response for key endpoints, the application's config dump, or a representative database record exported as JSON.
- Step 2Deploy and capture post-deployment state — After deployment, capture the same JSON state. Use the same API endpoint, the same config dump command, and the same record ID.
- Step 3Diff and validate changes — Paste pre-deployment JSON in the left panel and post-deployment JSON in the right panel. The diff shows every change. Verify each change was intentional and expected.
- Step 4Add to deployment runbook — Make JSON comparison a step in the deployment runbook: compare key API responses and config states before and after each deployment. The diff output becomes the deployment validation evidence.
Frequently asked questions
How do I diff database schema changes using JSON?+
Export the database schema as JSON using your database introspection tool (Prisma's JSON schema output, pg_dump --schema-only converted to JSON, or Drizzle's schema introspection). Diff the schema JSON before and after a migration to verify only the intended columns and tables changed.
What should I do if the diff shows unexpected changes?+
Stop the deployment rollout if changes are still in progress. If the deployment is complete, evaluate the severity: if unexpected changes are breaking (removed required fields, type changes), initiate a rollback. If changes are non-breaking (extra fields, no value changes), document and investigate the cause before the next deployment.
Is the deployment state data transmitted to JAD Apps?+
No. Diffing runs entirely in your browser. Pre and post-deployment state captures are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.