Defect Management

Attachments

Attachments provide the visual and contextual evidence that developers need to understand, reproduce, and fix a defect. A well-documented defect with clear screenshots or log files can reduce resolution time significantly by eliminating back-and-forth communication.

How to Add Attachments

1. Open the defect detail view by clicking on a defect in the defects list.
2. Scroll to the Attachments section.
3. Click the Upload button or drag and drop files into the attachment area.
4. The file is uploaded and associated with the defect immediately.

Supported File Types

Attachment Best Practices

• Always attach a screenshot for UI-related defects. A picture is worth a thousand words -- annotated screenshots with arrows or highlights pointing to the issue are even better.
• Include relevant log files for backend or API defects. Copy the relevant error stack trace or attach the full log file so developers can locate the issue quickly.
• Use screen recordings for defects that are timing-dependent or involve a sequence of user interactions that are hard to describe in text.
• Name files descriptively. Instead of "screenshot.png", use something like "checkout-discount-double-applied.png" so the context is clear even without opening the file.
• Compress large files. If your attachment is very large, consider compressing it (e.g., zipping log files) or trimming screenshots to show only the relevant portion of the screen.

Search & Filter

As your project accumulates defects over time, the ability to quickly find specific defects becomes essential. TestKase provides keyword search and multi-criteria filtering on the defects list view to help you locate defects efficiently.

Keyword Search

The search bar at the top of the defects list allows you to search by defect title. Type any keyword or phrase and the list will filter in real time to show only matching defects. Search is case-insensitive and matches partial words.

Filtering Options

Common Search Scenarios

• Release readiness check: Filter by Status = Open and Priority = Blocker or Critical to see all high-severity defects that could block a release.
• Developer workload: Filter by Assignee to see all defects assigned to a specific team member and understand their current workload.
• Verification queue: Filter by Status = Closed to find defects that are awaiting re-testing and verification. These defects have fixes applied but need a tester to confirm them.
• Triage meeting preparation: Filter by Status = Open to view the full defect backlog that needs to be assigned and prioritized during the next triage session.
• Area-specific investigation: Use keyword search to find all defects related to a specific feature (e.g., "checkout", "authentication", "reporting").

Defect Reports

TestKase includes several reports specifically designed to help you analyze defect trends and distributions. These reports are available in the Reports & Analytics section of your project and provide visual breakdowns of your defect data.

Available Defect Reports

Using Defect Reports Effectively

• Sprint retrospectives: Use the Defects by Cycle report to see how many defects were found in the current sprint compared to previous sprints. An upward trend may indicate code quality issues or increased scope that needs attention.
• Risk assessment: Use the Defects by Folder report to identify which modules or features have the highest defect density. These areas may need additional test coverage, code review attention, or architectural improvements.
• Team insights: Use the Defects by Tester report to understand testing effectiveness across your team. Testers who consistently find more defects in critical areas are valuable assets for high-risk testing assignments.
• Trend monitoring: Review defect reports at the end of each sprint or release cycle to track whether your defect rate is trending up or down over time. A decreasing trend indicates improving code quality.