qe-bug-reporting-excellence

Bug 报告最佳实践

<default_to_action> 报告 Bug 时：

1. 标题：[组件] 在[条件]下失败，导致[影响]
2. 描述：预期行为 → 实际行为 → 复现步骤
3. 包含：环境、严重程度、截图/日志、业务影响
4. 缩小范围：确定具体条件（浏览器、用户、金额阈值）
5. 一个 Bug = 一份报告（不要合并多个问题）

Bug 报告公式：

## [Component] Issue Title
**Severity:** Critical/High/Medium/Low
**Environment:** Production/Staging/Dev

### Expected Behavior
What should happen

### Actual Behavior
What actually happens (with error messages)

### Steps to Reproduce
1. Step one
2. Step two
3. Observe issue

### Impact
How this affects users/business

关键成功因素：

• 步骤可复现（100%）
• 环境信息完整（100%）
• 说明业务影响（90%）
• 提供截图或日志（80%） </default_to_action>

快速参考卡

严重程度级别

级别	定义	示例
Critical	系统宕机、数据丢失、安全问题	DB 被删除、支付故障、凭证泄露
High	主要功能故障、影响众多用户	无法结账、搜索故障、仪表板无法使用
Medium	部分功能故障，有变通方法	筛选器故障（刷新后可用）、导出缓慢
Low	外观问题、罕见边缘情况	按钮在移动设备上换行、工具提示颜色错误

标题公式

❌ 不佳：“结账功能故障” ✅ 良好：“订单总额超过 $1000 时，Visa 卡支付失败”

模式： [组件] 在[条件]下失败，导致[影响]

---

必要信息

环境详情

Browser: Chrome 120.0.6099.109 (Windows)
OS: Windows 11 Pro
URL: https://example.com/checkout
Date/Time: 2025-10-17 14:23 UTC
User: [email protected] (ID: 12345)
Request ID: abc-123-def-456

辅助证据

错误消息：

{
  "error": "Payment service unavailable",
  "code": "GATEWAY_TIMEOUT",
  "requestId": "abc-123-def-456"
}

控制台日志：

[ERROR] PaymentGateway: Connection timeout after 30000ms
  at PaymentGateway.charge (gateway.js:145)

---

示例：优秀的 Bug 报告

## [Checkout] Payment processing times out for orders > $1000

**Severity:** High
**Environment:** Production
**Affected Users:** ~15% of premium purchases

### Expected Behavior
Payment completes within 5 seconds regardless of amount.

### Actual Behavior
For orders above $1000, payment gateway times out after 30 seconds.
User sees "Payment failed" error. Order not created.

### Steps to Reproduce
1. Add items totaling $1,050 to cart
2. Proceed to checkout
3. Enter payment: Visa 4532 1234 5678 9010
4. Click "Place Order"
5. Wait 30+ seconds
6. Observe timeout error

### Environment
- Browser: Chrome 120 (Windows 11)
- User: [email protected]
- Request ID: abc-123-def-456

### Evidence
Console error: `PaymentGateway timeout: 30000ms exceeded`
Network: /api/checkout: 30.14s (timeout)

### Impact
- Lost revenue: ~$15K/week from failed orders
- 23 support tickets this week
- Affects 15% of orders over $1000

### Additional Context
Started after Oct 15 deployment (v2.3.0)
Possibly related to PR #456 (fraud check)

---

反模式

❌ 不佳	问题	✅ 良好
“结账功能坏了”	到底哪里无法使用？	“点击支付按钮时没有响应”
“我看到了错误”	没有复现步骤	提供包含具体条件的完整步骤
“页面加载很慢”	缺少具体信息	“仪表板需要 12 秒才能加载（应少于 3 秒）”
一份报告包含多个 Bug	无法分别跟踪	每个 Bug 单独提交一份报告

---

Agent 集成

// Automated bug triage
const triage = await Task("Triage Bug", {
  title: 'Payment fails for orders > $1000',
  description: bugDescription,
  steps: reproductionSteps
}, "qe-quality-analyzer");

// Returns: { severity, priority, component, suggestedAssignee, relatedIssues }

// Duplicate detection
const dupeCheck = await Task("Check Duplicates", {
  bugReport: newBug,
  similarityThreshold: 0.85
}, "qe-quality-analyzer");

// Bug report enhancement
const enhanced = await Task("Enhance Report", {
  originalReport: userSubmittedBug,
  addMissingInfo: true,
  identifyRootCause: true
}, "qe-production-intelligence");

---

Agent 协作提示

记忆命名空间

aqe/bug-reports/
├── triaged/*          - Bug triage results
├── duplicates/*       - Duplicate detection
├── patterns/*         - Recurring bug patterns
└── root-cause/*       - Root cause analyses

Fleet 协作

const bugFleet = await FleetManager.coordinate({
  strategy: 'bug-investigation',
  agents: [
    'qe-quality-analyzer',        // Triage and categorize
    'qe-flaky-test-hunter',       // Check if test-related
    'qe-production-intelligence'  // Check production logs
  ],
  topology: 'parallel'
});

---

相关技能

• technical-writing - 清晰地记录 Bug
• exploratory-testing-advanced - 发现 Bug
• sherlock-review - 调查根本原因

---

请记住

你的 Bug 报告是他人工作的起点。请确保报告完整（包含所需的全部信息）、清晰（任何人都能照着操作）、简洁（不包含无关内容），并且可执行（开发者知道下一步该做什么）。

优秀的 Bug 报告 = 更快修复 = 更好的产品 = 更满意的用户