Defect Management Tool used at Youtap is JIRA. A centralized repository for tracking and managing defects.
Defect Reporting
When a defect is identified during the test cycle, QA team must document it thoroughly in respective project in JIRA, including information on how to reproduce the issue, its severity, and any relevant screenshots or logs.
Defect Prioritization
Defects are assigned a priority level (e.g., critical, high, medium, low) based on their severity and impact on the software. Priority is determined collaboratively by the QA team, development team, and project stakeholders.
Defect Assignment
The defect is assigned to the responsible developer or team member for resolution. This assignment is typically based on the defect's nature and the developer's expertise.
Resolution and Verification
The developer works on resolving the defect. Once resolved, the defect is assigned back to the tester for verification. Testers ensure that the defect has been fixed and update the status accordingly.
Documentation Updates
Test cases and documentation are updated to reflect the changes made in response to the defect, ensuring that the test cases remain accurate.
Reporting and Metrics
Regular defect reports and metrics are generated to provide insights into the state of testing and defect management. These reports are shared with project stakeholders to inform decision-making.
More info here: Test Summary Report? What does it include? - Testing Center of Excellence - Confluence (atlassian.net)
Closure and Release
When all critical defects are resolved, and the software meets the exit criteria defined in the test plan, the testing phase is considered complete.