Is my test result data sent to a server?

No. All parsing and visualization runs 100% in your browser. Your SFDX test JSON — which contains class names and coverage data — never leaves your device.

How do I get the test result JSON from Salesforce?

Run "sf apex run test --result-format json --output-dir ./test-results" with SFDX CLI. Or use "sf apex run test --class-names MyClass --json". Paste the JSON output into this tool.

What is the minimum code coverage for production deployment?

Salesforce requires at least 75% overall Apex code coverage to deploy to production. Each individual trigger must have at least 1% coverage (some coverage). Classes with 0% coverage do not block deployment as long as the overall average is ≥75%.

What is line-level coverage?

Line-level coverage shows exactly which lines of code were executed during tests (covered) and which were not (uncovered). This helps you write targeted tests for the specific branches and conditions that are missing coverage.

How do I improve code coverage quickly?

Focus on uncovered branches rather than uncovered lines — an if/else with only the "if" branch tested counts as 50% covered. Use the line-level breakdown to find the exact conditions your tests are missing, then write test data that exercises those paths.

Dev Toolkit — 55+ Free Client-Side Developer Utilities

About the Apex Test Coverage Visualizer

Salesforce's 75% code coverage requirement is a deployment gate — not just a quality metric. When a deployment fails due to coverage, you need to know exactly which classes are below threshold and which lines are uncovered. This tool parses SFDX test result JSON and presents coverage as a heatmap, per-class table, and line-level breakdown so you can target your test writing precisely.

What this tool shows

Coverage Heatmap

Visual heatmap of all classes colored by coverage percentage — instantly see which classes are red (below 75%) and need attention.

Per-Class Breakdown

Sortable table of every class with covered lines, total lines, and coverage percentage. Filter to show only classes below threshold.

Line-Level Detail

Drill into any class to see exactly which lines are covered (green) and uncovered (red) — the precise information needed to write targeted tests.

Test Failures

Failed test methods with assertion messages and stack traces — fix failing tests before worrying about coverage percentages.

Pipeline

Deploy Status Analyzer — analyze the full deployment result including coverage.
Debug Log Analyzer — debug failing test methods with log analysis.
Apex Trigger Builder — generate trigger scaffolds with test class templates.

Frequently asked

Is my test result data sent to a server?: No. All parsing and visualization runs 100% in your browser. Your SFDX test JSON — which contains class names and coverage data — never leaves your device.
How do I get the test result JSON from Salesforce?: Run "sf apex run test --result-format json --output-dir ./test-results" with SFDX CLI. Or use "sf apex run test --class-names MyClass --json". Paste the JSON output into this tool.
What is the minimum code coverage for production deployment?: Salesforce requires at least 75% overall Apex code coverage to deploy to production. Each individual trigger must have at least 1% coverage (some coverage). Classes with 0% coverage do not block deployment as long as the overall average is ≥75%.
What is line-level coverage?: Line-level coverage shows exactly which lines of code were executed during tests (covered) and which were not (uncovered). This helps you write targeted tests for the specific branches and conditions that are missing coverage.
How do I improve code coverage quickly?: Focus on uncovered branches rather than uncovered lines — an if/else with only the "if" branch tested counts as 50% covered. Use the line-level breakdown to find the exact conditions your tests are missing, then write test data that exercises those paths.