Is my deployment data sent to a server?

No. All parsing and analysis runs 100% in your browser. Your deployment JSON — which may contain class names and test results — never leaves your device.

How do I get the deployment JSON from Salesforce?

Use SFDX CLI: "sf project deploy start --json > deploy-result.json". Or retrieve an existing deployment via the Metadata API: "sf project deploy report --job-id --json". Paste the JSON output into this tool.

What causes a deployment to fail?

Common causes: Apex test failures (tests must pass with ≥75% coverage), compile errors in Apex classes or triggers, missing metadata dependencies, validation rule conflicts, or insufficient permissions on the target org.

What is the 75% code coverage requirement?

Salesforce requires that at least 75% of your Apex code is covered by unit tests before you can deploy to a production org. Each individual trigger must also have some coverage. This requirement does not apply to sandbox deployments.

What is a quick deploy?

A quick deploy reuses the test results from a recent validated deployment, skipping the test run. This reduces deployment time significantly for large orgs. The validation must have passed within the last 10 days.

Deployment Status Dashboard

Paste a Salesforce Metadata API deploy result JSON (from checkDeployStatus or sf deploy metadata --json) to visualize component errors, test failures, and code coverage.

Paste Deploy Result JSON

About the Salesforce Deploy Status Analyzer

Salesforce deployments produce verbose JSON output that's difficult to parse at a glance — especially when a deployment fails and you need to find the root cause quickly. This tool parses the deployment result JSON and presents a clear summary: overall status, component errors, test failures, code coverage breakdown, and a timeline of the deployment phases.

What this tool shows

Deployment Summary

Overall status, component counts (deployed / failed / total), test results, and code coverage percentage at a glance.

Component Errors

Failed components listed with their error messages and line numbers — the exact information you need to fix the deployment.

Test Failures

Failed test methods with stack traces and assertion messages — pinpoints exactly which test is blocking your deployment.

Coverage Breakdown

Per-class code coverage percentages — identifies which classes are below the 75% threshold and blocking production deployment.

Pipeline

Test Coverage Visualizer — deeper analysis of your test coverage results.
Debug Log Analyzer — analyze logs from failing test methods.
Apex Trigger Builder — scaffold triggers with proper test coverage built in.

Frequently asked

Is my deployment data sent to a server?: No. All parsing and analysis runs 100% in your browser. Your deployment JSON — which may contain class names and test results — never leaves your device.
How do I get the deployment JSON from Salesforce?: Use SFDX CLI: "sf project deploy start --json > deploy-result.json". Or retrieve an existing deployment via the Metadata API: "sf project deploy report --job-id <id> --json". Paste the JSON output into this tool.
What causes a deployment to fail?: Common causes: Apex test failures (tests must pass with ≥75% coverage), compile errors in Apex classes or triggers, missing metadata dependencies, validation rule conflicts, or insufficient permissions on the target org.
What is the 75% code coverage requirement?: Salesforce requires that at least 75% of your Apex code is covered by unit tests before you can deploy to a production org. Each individual trigger must also have some coverage. This requirement does not apply to sandbox deployments.
What is a quick deploy?: A quick deploy reuses the test results from a recent validated deployment, skipping the test run. This reduces deployment time significantly for large orgs. The validation must have passed within the last 10 days.

Related Tools

SOQL Query Builder

Build SOQL queries visually with field autocomplete.

SF Object Field Analyzer

Analyze Salesforce object fields from describe API responses.

Permission Set Diff

Compare two Salesforce Permission Set XMLs side by side.

Debug Log Analyzer

Analyze Apex debug logs with flame tree, governor limits & SOQL breakdown.

LWC Scaffolder

Generate Lightning Web Component boilerplate files with a visual wizard.

Apex Code Metrics

Static analysis of Apex code — LOC, cyclomatic complexity, method classification, nesting depth.