The page itself is a thin wrapper around the Apex Test Framework. Most of the value comes from maintaining Test Suites that map to real subsystems and running them at the right moments.
- Define Test Suites
Setup, Custom Code, Apex Test Suites. Create suites that map to real subsystems: Sales Cloud Smoke, Service Cloud Regression, Integration Layer, and so on.
- Open Application Test Execution
Setup, Custom Code, Application Test Execution. Click Select Suites and choose the suite you want to run.
- Submit and watch progress
Click Run. The page polls and updates pass/fail counts per class. The run is async, so walking away is fine.
- Drill into failures
Click any failed class to view the offending method, the assertion message, and the stack trace. Cross-reference with Apex Jobs if the run involved async paths.
- Review history and trend
Open Application Test History to compare the latest run against prior runs. Sustained pass-rate or coverage drops surface trends that single-run inspection misses.
- Suite pass rate is not deploy readiness. The 75 percent overall coverage rule still applies at production deploy time.
- Stale suites are misleading. Tests added to the codebase do not automatically join a suite; maintenance matters.
- Parallel execution can break tests that share data. Fix the data isolation; disabling parallel testing globally is a heavy hammer.
- Retention is short. Export ApexTestResult rows weekly for any trend analysis longer than a few weeks.