Best Practices & FAQ
Guidelines for effective reporting and answers to common questions.
Best Practices
Follow these best practices to get the most value from TestKase's reporting suite.
1. Establish quality gates with reports
Define minimum pass rate thresholds (e.g., 95% for critical tests, 85% overall) and check the Execution Summary report before every release. The Release Readiness gauge can serve as a formal go/no-go metric — read the FAQ below before you pick a threshold for it.
2. Review reports in daily stand-ups
Start each daily stand-up by pulling up the Execution Summary and Tester Workload reports. This takes 30 seconds and gives the entire team visibility into where things stand and who needs help.
3. Use trend reports for retrospectives
During sprint retrospectives, review Execution Trend and Created vs Executed reports. Are failure rates improving? Is test creation keeping pace with feature development? These trend lines tell the story of your team's quality journey.
4. Act on the insight reports, do not just read them
Insight reports like Flaky Tests, Predictive Failure, and Suite Optimization are only valuable if you act on their findings. Create action items: fix flaky tests, run predicted failures first, archive redundant tests. Track progress over time.
5. Maintain requirement traceability
Link every test case to at least one requirement and vice versa. Regularly check the Uncovered Requirements and Unlinked Test Cases reports to keep your traceability matrix complete. This is especially important for regulated industries.
6. Structure folders to match your architecture
Reports like Execution by Folder, Scorecard by Folder, and Risk Heatmap (Folder) are most meaningful when your folder structure mirrors your product architecture. Create folders for each module or feature area so these reports provide actionable, module-level insights.
7. Use burn-down charts for deadline tracking
At the start of each test cycle, check the Execution Burn-Down chart daily. If the line is not declining steadily toward zero, you are falling behind. Take corrective action early (reassign tests, add testers, reduce scope) rather than discovering the delay at the end.
8. Schedule quarterly suite optimization
Every quarter, generate the Suite Optimization and Stale Tests insight reports. Archive or update tests that are no longer providing value. A leaner, more focused test suite executes faster and produces more meaningful results.
FAQ
▶How do I access the Reports tab?
Navigate to your project from the left sidebar then click on the Reports tab in the project navigation. All available reports are displayed as cards organized by category. Click any card to open that report with default filters.
▶Can I export reports as PDF or images?
Report charts can be viewed in the Reports tab within the application. For raw data exports, use the CSV export functionality available on test cycles and test cases to extract the underlying data. PDF and image export features are on the roadmap.
▶How often are reports updated?
Reports are generated in real time based on the latest data. There is no caching delay -- what you see reflects the current state of your project. Every time you open a report or change a filter, the chart is recalculated from live data.
▶Do Insight reports cost credits?
No. Insight (Tier 3) reports are computed directly from your project's execution data using advanced analytics and heuristic scoring -- they do not consume any AI credits. No report tier consumes credits. AI credits are only used by AI Test Case Generation and the AI Agent. See the AI Features guide for details on how credits work.
▶What is the difference between Tier 1, Tier 2, and Tier 3 reports?
The tiers group reports by complexity, not by plan -- every report is available on every plan. Tier 1 (Core) reports show point-in-time snapshots: execution summaries, coverage percentages, defect distributions, and team workload. Tier 2 (Trends) reports add a time dimension with trend lines, burn-up/down charts, and scorecards. Tier 3 (Insights) reports use advanced analytics and heuristic scoring; they are always available, whatever your organization's AI settings, and do not consume any AI credits to generate.
▶Why does a report show no data?
Reports require the relevant data to exist. If an execution report shows no data, verify that test cases have been executed within the selected date range and cycle. If a coverage report shows no data, verify that requirements have been created and linked to test cases. Check your filters -- a narrow date range or specific cycle filter may exclude all matching data.
▶Can I see reports across multiple projects?
Reports are scoped to a single project. Each project has its own Reports tab with data isolated to that project. Cross-project analytics are not currently available but are being considered for future releases.
▶I have seen Failed Requirements or Project Health mentioned — why can't I find them in the Reports tab?
Five reports exist only in the TestKase API: Failed Requirements, Smart Prioritization, Defect Hotspots, Requirement Risk Matrix and Project Health. They have no card in the Reports tab, so no amount of scrolling will find them, and they are not counted in the 37. Call them with a personal access token or through the MCP server — see Reports Available Only Through the API.
▶Does a table report show every matching row?
No. The table reports are capped: Test Case Quality, Stale Tests and Suite Optimization return the top 100 rows, and Flaky Tests and Predictive Failure return the top 50. The rows are sorted worst-first, so the cap hides the least urgent rows -- but if you are using one of these reports to measure the size of a problem, remember that a full-looking table may be a truncated one. Narrow the report with a cycle or date filter to see a different slice.
▶What does the granularity filter do?
The granularity filter controls how time periods are grouped on the X-axis of trend charts. Daily shows one data point per day -- best for sprint-level analysis. Weekly aggregates data by week -- best for release-level views, and is the default. Monthly aggregates by month -- best for quarterly reviews. Granularity is available on the six time-series trend reports (Execution Trend, Execution Burn-Up, Execution Burn-Down, Test Creation Trend, Created vs Executed, Requirement Coverage Trend) and on the Execution Velocity insight report. The other Tier 2 reports have no granularity filter.
▶How does the Release Readiness gauge calculate its score?
The Release Readiness score is a weighted composite of three factors: overall pass rate (what percentage of executed tests passed), execution progress (what percentage of tests in scope have been executed), and critical test pass rate. The weights are pass rate 45%, execution progress 30%, critical pass rate 25%, combined into a single 0-100 score. The gauge is teal at 75 and above, amber from 50, orange from 25, and red below 25.
"Critical" here means a test case whose priority is P0 or P1. The default test-case priority
list is Blocker, Critical, Major, Minor, Trivial, so in a default project no test case matches and
that 25% component always scores 0 -- a fully passing, fully executed project reads about 75. Set
test-case priorities to P0/P1 if you want this component to contribute.
▶How can I identify and fix flaky tests?
Generate the Flaky Tests insight report to get a list of tests with inconsistent results. For each flaky test, review recent execution history to understand the pattern. Common root causes include timing-dependent assertions, shared test data, external service dependencies, and non-deterministic ordering. Fix the root cause, then re-run the test several times to confirm stability.