常见的做法是将执行计划置于表示不同测试区域或目的的层次结构中。在某些情况下,例如要了解测试状态,进而确定一个区域或目的的质量,您需要了解总体通过、失败和未执行计数。
使用数据集市视图 RV_ExecutionPlanStatusRollup 为特定执行计划文件夹创建报告,以返回按内部版本分组的通过、失败和未执行计数。
SELECT BuildName, PassedCount, FailedCount, NotExecutedCount
FROM RV_ExecutionPlanStatusRollup
WHERE ExecutionFolderID = ${executionPlanID|43|Execution Plan ID}| BuildName | PassedCount | FailedCount | NotExecutedCount | 
|---|---|---|---|
| 351 | 0 | 0 | 2 | 
| 352 | 15 | 7 | 1 | 
SELECT eps.BuildName, eps.ExecutionPlanID, SUM(eps.PassedCount) PassedCount,
  SUM(eps.FailedCount) FailedCount, SUM(eps.NotExecutedCount) NotExecutedCount
FROM RV_ExecutionPlanStatusPerBuild eps
INNER JOIN TM_ExecTreePaths etp ON eps.ExecutionPlanID = etp.NodeID_pk_fk
WHERE etp.ParentNodeID_pk_fk = ${execFolderID|44|Execution Folder ID}
GROUP BY eps.ExecutionPlanID, eps.BuildOrderNumber, eps.BuildName
ORDER BY eps.BuildOrderNumber, eps.ExecutionPlanID| BuildName | ExecutionPlanID | PassedCount | FailedCount | NotExecutedCount | 
|---|---|---|---|---|
| 351 | 2307 | 0 | 0 | 2 | 
| 352 | 2184 | 11 | 2 | 0 | 
| 352 | 2185 | 0 | 3 | 0 | 
| 352 | 2186 | 2 | 1 | 0 | 
| 352 | 2187 | 1 | 0 | 0 | 
| 352 | 2191 | 0 | 1 | 0 | 
| 352 | 2307 | 1 | 0 | 1 |