Token导航 LogoToken导航TokenDH.com
研究检索操作浏览器github未标认证来源可访问许可证需确认审计通过

test-quality-analysis测试质量分析

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

总安装

870

周安装

37

GitHub Stars

28

下载量

305
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:test-quality-analysis(测试质量分析)
来源仓库:https://github.com/laurigates/claude-plugins
仓库路径:skills/test-quality-analysis
安装命令:
npx skills add https://github.com/laurigates/claude-plugins --skill test-quality-analysis
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/laurigates/claude-plugins --skill test-quality-analysis

简介

test-quality-analysis 用于辅助测试设计和回归验证。

  • 适合编写单元测试、端到端测试或分析失败日志。
  • 使用时需确认项目测试框架和运行命令。test-quality-analysis 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 涉及浏览器或外部服务时应区分本地模拟与生产环境。
  • 确保测试逻辑真实,不为了通过而破坏原有功能。

SKILL.md

Test Quality Analysis

Expert knowledge for analyzing and improving test quality - detecting test smells, overmocking, insufficient coverage, and other testing anti-patterns.

When to Use This Skill

Use this skill when...Use another skill instead when...
Reviewing test quality and smellsWriting new unit tests (use vitest-testing)
Detecting overmocking or flaky testsSetting up E2E tests (use playwright-testing)
Analyzing test coverage gapsValidating tests via mutation (use mutation-testing)
Improving test maintainabilityGenerating test data (use property-based-testing)
Auditing test suites for anti-patternsWriting Python tests (use python-testing)

Core Expertise

Test Quality Dimensions

  • Correctness: Tests verify the right behavior
  • Reliability: Tests are deterministic and not flaky
  • Maintainability: Tests are easy to understand and modify
  • Performance: Tests run quickly
  • Coverage: Tests cover critical code paths
  • Isolation: Tests don't depend on external state

Test Smells - Quick Reference

SmellSymptomFix
Overmocking3+ mocks per test; mocking pure functionsMock only I/O boundaries; use real implementations
Fragile testsBreak on refactor without behavior changeTest public APIs; use semantic selectors
Flaky testsNon-deterministic pass/failProper async/await; mock time; ensure isolation
Test duplicationCopy-pasted setup across testsExtract to beforeEach(), fixtures, helpers
Slow testsSuite > 10s for unit testsbeforeAll() for expensive setup; parallelize
Poor assertionstoBeDefined(), no assertions, mock-only assertionsSpecific matchers; assert outputs and state
Insufficient coverageCritical paths untested80%+ on business logic; test error paths and boundaries

Analysis Tools

TypeScript/JavaScript

vitest --coverage                              # Coverage report
vitest --coverage --coverage.thresholds.lines=80  # Threshold check
vitest --reporter=verbose                      # Find slow tests

Python

uv run pytest --cov --cov-report=term-missing  # Coverage with missing lines
uv run pytest --cov --cov-fail-under=80        # Threshold check
uv run pytest --durations=10                   # Find slow tests

Key Anti-Patterns

Testing Implementation vs Behavior

// BAD: Testing how
test('uses correct algorithm', () => {
  const spy = vi.spyOn(Math, 'sqrt')
  calculateDistance({ x: 0, y: 0 }, { x: 3, y: 4 })
  expect(spy).toHaveBeenCalled()
})

// GOOD: Testing what
test('calculates distance correctly', () => {
  const distance = calculateDistance({ x: 0, y: 0 }, { x: 3, y: 4 })
  expect(distance).toBe(5)
})

Weak Assertions

// BAD
expect(users).toBeDefined()     // Too vague
expect(mockAPI).toHaveBeenCalled() // Testing mock, not behavior

// GOOD
expect(user).toMatchObject({
  id: expect.any(Number),
  name: 'John',
  email: 'john@example.com',
})

Missing Coverage

// BAD: Only tests happy path
test('applies discount', () => {
  expect(calculateDiscount(100, 'SAVE20')).toBe(80)
})

// GOOD: Tests all paths
describe('calculateDiscount', () => {
  it('applies SAVE20', () => expect(calculateDiscount(100, 'SAVE20')).toBe(80))
  it('applies SAVE50', () => expect(calculateDiscount(100, 'SAVE50')).toBe(50))
  it('invalid coupon', () => expect(calculateDiscount(100, 'INVALID')).toBe(100))
  it('no coupon', () => expect(calculateDiscount(100)).toBe(100))
})

Test Structure (AAA Pattern)

test('user registration flow', async () => {
  // Arrange
  const userData = { email: 'user@example.com', password: 'secure123' }
  const mockEmailService = vi.fn()

  // Act
  const user = await registerUser(userData, mockEmailService)

  // Assert
  expect(user).toMatchObject({ email: 'user@example.com', emailVerified: false })
  expect(mockEmailService).toHaveBeenCalledWith('user@example.com', expect.any(String))
})

Agentic Optimizations

ContextCommand
Coverage check (TS)vitest --coverage --reporter=dot
Coverage check (Python)uv run pytest --cov --cov-fail-under=80 -q
Find slow tests (TS)vitest --reporter=verbose
Find slow tests (Python)uv run pytest --durations=10 -q
Missing lines (Python)uv run pytest --cov --cov-report=term-missing

For detailed examples, advanced patterns, and best practices, see REFERENCE.md.

See Also

  • vitest-testing - TypeScript/JavaScript testing
  • python-testing - Python pytest testing
  • playwright-testing - E2E testing
  • mutation-testing - Validate test effectiveness

References

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.38%
按下载量换算108

Claude

31.76%
按下载量换算97

Cursor

19.29%
按下载量换算59

Gemini CLI

10.45%
按下载量换算32

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills