The page is a thin UI over standard test-run records. Most of the value comes from reading it consistently as part of a release cadence, not from one-off visits.
- Open Application Test History
Setup, Custom Code, Application Test History. Default view shows recent runs in reverse chronological order.
- Filter to relevant runs
Apply filters by user, suite, status, and date range. Save a view for release-validation runs so the team can return to it quickly.
- Compare consecutive runs
Pick the two most recent runs of the target suite. Compare pass rate, elapsed time, and failure list. Regressions usually appear as one or two new failed methods that succeeded the last run.
- Drill into failures
Click failed runs. Read the stack trace and assertion message. Cross-reference with Apex Jobs if the failure involves async paths.
- Export for trend analysis
Schedule a batch job that copies ApexTestRunResult and ApexTestResult rows to a custom history object weekly. Build a Lightning dashboard on top for quarterly retrospectives.
- Retention is weeks, not months. Plan a snapshot pipeline for any trend analysis beyond a few weeks.
- Aggregate pass counts can hide flaky tests. Per-method history is the only reliable signal for intermittent failures.
- Code coverage is not on the page. Check the Code Coverage page separately before any production deploy.
- Cancelled runs appear in history with partial data. They are useful only for run-start metadata, not for outcome analysis.