Testing-tools/bug-report-template.md

62 lines
1.6 KiB
Markdown

## Bug ID: []
**Title:**
**Reported By:**
**Reported Date:** [YYYY-MM-DD]
**Priority:** [P1-Critical/P2-High/P3-Medium/P4-Low]
**Severity:** [Blocker/Critical/Major/Minor/Cosmetic]
**Status:** [New/In Progress/Fixed/Verified/Closed]
**Assigned To:** [Developer name]
### Environment:
- **Application Version:** [e.g., v1.2.3]
- **Browser/Device:** [e.g., Chrome 120.0.6099.109/iPhone 14]
- **Operating System:** [e.g., Windows 11/macOS 14.0/iOS 17]
- **Test Environment:** [e.g., Development/QA/Staging/Production]
### Description:
[Detailed description of the bug]
### Steps to Reproduce:
1. [Clear step-by-step instructions to reproduce the bug]
2. [Example: Navigate to the to-do app homepage]
3. [Example: Add a new task with emoji characters in the title]
4. [Example: Click the "Save" button]
### Expected Result:
[What should happen when following the steps above]
### Actual Result:
[What actually happens when following the steps above]
### Visual Proof:
[Placeholder for screenshots/screen recordings that demonstrate the issue]
### Console Logs:
```
[Any relevant console errors or logs]
```
### Additional Information:
- [Test data used]
- [User account details (if applicable)]
- [Any workarounds discovered]
- [Previous related bugs]
### Root Cause Analysis (to be filled by developer):
[Technical explanation of what caused the bug]
### Fix Details (to be filled by developer):
[Description of how the bug was fixed]
### Verification Steps (to be filled by QA):
1. [Steps to verify the bug fix]
2. [Example: Repeat the steps to reproduce and confirm the issue no longer occurs]
3. [Example: Check that the fix doesn't introduce new issues]