An execution trace
for every test run.
Salesforce gives you a 40,000-line debug log and a replay debugger. Nimbus instruments every test execution with OpenTelemetry (method calls, SOQL, DML, triggers, branches, variables) and shows it as an interactive execution tree.
A debug log next to a trace
Coverage by line, method, and branch
Coverage is tracked at three levels: lines, methods, and branches. After every run, you see a summary with progress bars and a per-class breakdown - which classes are covered, which methods were called, and which weren't.
The color coding matches Salesforce's own thresholds: green at 80% and above, amber between 50% and 80%, red below. You know your deployment coverage status before you push.
Branch coverage goes further than Salesforce's built-in metric - it tracks whether both sides of every if, switch, and ternary were exercised.
Test analytics
Every test run is recorded. Over time, Nimbus builds a picture of your test suite's health - pass rate trends, duration trends, and automatic flaky test detection.
The trend chart shows pass rate and duration for every run over the last N days. Regressions are immediately visible - a sudden dip in pass rate or a spike in duration pinpoints exactly when something changed.
Flaky test detection tracks whether each test passes or fails across runs and computes a flip rate - the fraction of adjacent runs where the outcome changed. A test with a 40% flip rate is unreliable.
Where to find it
Traces and analytics are always on, with no configuration required. Every test run is recorded and every execution is traced.
In the Dev UI, the Analytics tab shows the trend chart, flaky test list, and run history. Click any test in the Results tab to open its trace inline.
In VS Code and IntelliJ, the Nimbus panel includes history, trend charts, and the trace viewer. Right-click any test to open its trace directly in the editor.
From the terminal, use nimbus trace to open the interactive two-panel trace viewer for any recent test.
# Run a test with tracing enabled
nimbus test "AccountServiceTest.testCreate" --trace
# Set trace verbosity
nimbus test "AccountServiceTest.*" --trace --trace-level verbose
# levels: minimal, normal, verbose, debug
# Traces are saved to:
# .nimbus/traces/<timestamp>_<run-id>/trace.jsonl
# History is saved to:
# .nimbus/history/<timestamp>_<run-id>.jsonNimbus records what every test did.
Every method call, query, and branch is recorded in a structured, searchable trace. There are no log files and no replay setup.