SmartTest Execution

Short answer

Query run history with list_execution_history, pull failing jobs via fetch_execution_report, and manage semantic-similar clusters for cleanup workflows.

Common scenarios

Debug a failed batch

fetchExecutionReport — provide batchInvocationId and/or jobId. Always includes batchViewUrl when a batch id is known.

Browse history

listExecutionHistory (aggregate=true for suite timing only), listExecutionJobDimensionValues

Semantic similarity

listSemanticSimilarTests, setEntityDistinct

Related

• API Basics
• Interactive API Reference

Frequently asked questions

How do I get failing test details?

fetch_execution_report with batchInvocationId and/or jobId. batchViewUrl is always included when a batch id is known.

Related pages

• Release Management
• Issue Management
• Release Checks