testing-usability

可用性测试

测试应用的可用性、用户体验和交互设计，补充功能测试和无障碍测试。

何时使用

在以下情况下使用此技能：

• 评估用户界面设计的有效性
• 测试导航和工作流是否直观
• 收集定性用户反馈
• 提升用户满意度和参与度
• 验证信息架构
• 测试新用户的易学性

我能做什么

• 用户体验评估：

  • 测量任务成功率
  • 测量任务完成时间
  • 分析错误率和错误恢复情况
  • 对用户满意度进行评分

• 交互设计测试：

  • 导航是否直观
  • 表单设计和工作流
  • 信息层级
  • 视觉设计效果

• 用户研究方法：

  • 用户访谈和观察
  • 出声思考法
  • 用卡片分类法梳理信息架构
  • 通过 A/B 测试比较设计方案

• 与其他测试类型协同：

  • 以功能测试为基础（确保功能正常）
  • 补充无障碍测试（确保所有人都能使用）
  • 为视觉设计测试提供参考（美观性 + 可用性）
  • 为性能测试提供背景信息（感知速度）

示例

# Usability testing tools and methods
npm run test:usability:survey      # User satisfaction surveys
npm run test:usability:analytics    # Analytics-based usability metrics

# User testing coordination
# Manual process typically, but can coordinate with:
npm run test:e2e:usability         # E2E tests with usability focus
npm run test:accessibility         # Accessibility complements usability

# Heatmap and session recording setup
# Tools: Hotjar, FullStory, Microsoft Clarity

# A/B testing framework
npm run test:ab:deploy             # Deploy A/B test variations
npm run test:ab:analyze            # Analyze A/B test results

# Coordinate with functional testing
npm run test:usability -- --functional-coverage
npm run test:e2e -- --usability-focus

输出格式

Usability Test Results:
──────────────────────────────
Test Method: Remote unmoderated testing with 15 participants
Testing Period: 2 weeks

Task Completion Rates:
  ✅ User Registration: 93% success (14/15)
  ✅ Product Search: 87% success (13/15)
  ⚠️ Checkout Process: 73% success (11/15)
    - 3 users confused by shipping options
    - 1 user abandoned due to form length

Time to Complete Key Tasks:
  - Registration: 2.1 minutes (target < 3 minutes)
  - Find Product: 1.4 minutes (target < 2 minutes)  
  - Complete Purchase: 4.7 minutes (target < 5 minutes)

Error Rates and Recovery:
  - Form errors: 22 total, 18 self-corrected
  - Navigation errors: 8, all recovered
  - Critical errors: 2 (checkout abandonment)

User Satisfaction (1-5 scale):
  - Ease of use: 4.2
  - Navigation: 3.8  
  - Visual design: 4.5
  - Overall satisfaction: 4.1

Integration with Other Testing:
  - Functional tests pass, but usability reveals workflow issues
  - Accessibility compliant, but not optimally usable
  - Performance acceptable, but perceived speed could improve
  - Security features add friction to user experience

Key Findings:
  1. Checkout process needs simplification
  2. Search functionality effective but could be more prominent
  3. Mobile navigation needs improvement
  4. Users appreciate clean design but want more guidance

Recommendations:
  - Simplify checkout form (reduce fields by 30%)
  - Improve mobile hamburger menu discoverability
  - Add progress indicators to multi-step processes
  - Implement tooltips for complex features

注意事项

• 可用性测试侧重定性分析，可补充定量测试
• 应邀请真实用户参与测试，而不仅是开发者或测试人员
• 考虑不同的用户画像和技能水平
• 可用性测试应采用迭代方式，而非只进行一次
• 结合分析数据，全面了解情况
• 记录用户遇到的问题和成功案例
• 根据影响和工作量确定可用性改进的优先级
• 考虑不同文化背景对可用性的期望差异
• 在可用性与安全性、性能及其他要求之间取得平衡