Defect Reports
Analyze defect distribution by folder, cycle, and tester.
Defect Analytics
Defect analytics reports help you understand where defects are being found and who is finding them. These reports are essential for root cause analysis and for focusing development effort on the most defect-prone areas.
Defects by Folder
Chart type: Donut | Tier: 1
Displays defect distribution across test case folders. The donut chart segments represent each folder, with the size of each segment proportional to the number of defects found in that folder's test cases.
Key insights: Folders with disproportionately high defect counts indicate areas of the product that are unstable or under-developed. These areas may benefit from additional code review, refactoring, or more thorough test coverage.
When to use: After a test cycle completes, review defect distribution to identify problem areas. Share with the development team during bug triage to prioritize stabilization efforts.
Defects by Cycle
Chart type: Donut | Tier: 2
Shows defect counts per test cycle. This helps you compare defect discovery rates across different testing phases -- for example, how many defects were found during smoke testing vs. regression testing vs. exploratory testing.
Key insights: A high defect count in early cycles (smoke, sanity) is a warning sign that the build is unstable. If regression cycles are finding many new defects, it may indicate that recent code changes introduced regressions.
When to use: During release planning to compare defect rates across testing phases and assess build stability.
Defects by Tester
Chart type: Donut | Tier: 2
Shows how many defects each tester has discovered. This is not a performance evaluation -- it reflects which testers are working in the most defect-rich areas and contributing the most to defect discovery.
Key insights: Testers finding many defects may be testing higher-risk features or using more effective testing techniques. Testers finding very few defects may be testing stable areas, or their test cases may need review for thoroughness.
When to use: During retrospectives to discuss defect discovery patterns and refine testing assignments for the next cycle.
Defects in TestKase are linked to test executions. To learn more about how defects are created and tracked, see the Defects guide.