Execution Reports

Execution Reports

Execution reports are the most commonly used reports in TestKase. They show pass/fail/blocked breakdowns across different dimensions -- giving you instant clarity on where testing stands. All six execution reports are Tier 1 and available on every plan.

Execution Summary

Chart type: Donut | Tier: 1

Provides an overall pass/fail/blocked breakdown across all test executions in the selected scope. The donut chart shows the percentage and count for each status, giving you a single at-a-glance view of execution health.

Key insights: Overall pass rate percentage, proportion of blocked tests that may indicate environment or dependency issues, and the ratio of remaining unexecuted tests.

When to use: Use this as your daily stand-up dashboard view. Check it before release decisions to verify overall pass rate meets your quality gates.

Execution by Cycle

Chart type: Stacked Bar | Tier: 1

Displays a stacked status view of each test cycle's execution results. Each bar represents a test cycle, with segments showing passed, failed, blocked, and unexecuted counts.

Key insights: Compare execution progress across cycles at a glance. Identify which cycles have high failure rates or are falling behind on execution.

When to use: When managing multiple test cycles within a release and you need to compare their progress side by side. Especially useful for regression vs. smoke vs. sanity cycle comparisons.

Execution by Tester

Chart type: Stacked Bar | Tier: 1

Compares execution outcomes across individual testers. Each bar represents a tester, showing how many tests they passed, failed, or had blocked.

Key insights: Identify workload imbalances -- some testers may have significantly more assignments than others. Spot testers who are encountering high failure rates, which may indicate they are testing more complex or unstable features.

When to use: During sprint retrospectives to review workload distribution, or when planning the next cycle to rebalance assignments.

Execution by Priority

Chart type: Stacked Bar | Tier: 1

Shows status distribution grouped by test case priority level (Critical, High, Medium, Low). Each priority level gets its own bar with stacked pass/fail/blocked segments.

Key insights: Verify that Critical and High priority tests have been executed first and are passing. A high failure rate on critical-priority tests is a strong signal that the release is not ready.

When to use: Before release sign-off. If your critical tests show a low pass rate, it is a clear indicator to hold the release and investigate.

Execution by Environment

Chart type: Stacked Bar | Tier: 1

Splits execution results by target environment (e.g., Development, Staging, Production, QA). This report helps you understand whether failures are environment-specific or systemic.

Key insights: If failures cluster in a specific environment, the root cause is likely environmental (configuration, data, infrastructure) rather than a code defect. Conversely, failures across all environments point to a genuine bug.

When to use: When troubleshooting test failures to isolate whether the issue is environment-specific. Also useful for verifying that staging mirrors production behavior.

Execution by Folder

Chart type: Stacked Bar | Tier: 1

Shows the latest execution status of each test case, grouped by folder. Only the most recent meaningful execution across all test cycles is counted, providing a clean view of current status per module or feature area.

Key insights: Identify which feature areas (folders) have the highest failure rates. This helps direct debugging efforts toward the most problematic modules.

When to use: When you want a module-level quality view. Particularly useful if your folder structure mirrors your product architecture (e.g., "Authentication", "Payments", "User Management").