qa/test-execution
- Repo stars 433
- Author updated Live
- Author repo boss-skill
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 92 / 100 · audit passed
- Author / version / license
- @echoVic · v1.0.0 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Node.js · Python
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: qa/test-execution
description: | 语言 | 单元测试 | E2E测试 | |------|----------|---------| | Node.js | npm test | npx playwright test |…
category: engineering
runtime: Node.js / Python
---
# qa/test-execution output preview
## PART A: Task fit
- Use case: | 语言 | 单元测试 | E2E测试 | |------|----------|---------| | Node.js | npm test | npx playwright test | | Python | pytest | pytest tests/e2e | | Go | go test ./... | - | runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “强制要求：真实执行测试 / 测试执行流程 / 测试框架检测” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “| 语言 | 单元测试 | E2E测试 | |------|----------|---------| | Node.js | npm test | npx playwright test | | Python | pytest | pytest tests/e2e | | Go | go test ./... | - | runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “强制要求：真实执行测试 / 测试执行流程 / 测试框架检测” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “强制要求：真实执行测试 / 测试执行流程 / 测试框架检测”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: qa/test-execution
description: | 语言 | 单元测试 | E2E测试 | |------|----------|---------| | Node.js | npm test | npx playwright test |…
category: engineering
source: echoVic/boss-skill
---
# qa/test-execution
## When to use
- | 语言 | 单元测试 | E2E测试 | |------|----------|---------| | Node.js | npm test | npx playwright test | | Python | pytest | p…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “强制要求：真实执行测试 / 测试执行流程 / 测试框架检测” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "qa/test-execution" {
input -> user goal + target files + boundaries + acceptance criteria
context -> 强制要求：真实执行测试 / 测试执行流程 / 测试框架检测
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js / Python | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}测试执行方法
强制要求：真实执行测试
你必须真正执行测试，禁止生成 Mock 数据！
测试执行流程
- 检测项目类型和测试框架
- 根据项目类型执行测试
- 执行 E2E / 集成测试
- 解析测试输出（总数、通过数、失败数、覆盖率）
测试框架检测
JavaScript/TypeScript
- Jest:
jest.config.js,"jest"in package.json - Vitest:
vitest.config.js,"vitest"in package.json - Playwright:
playwright.config.js - Cypress:
cypress.json
Python
- pytest:
pytest.ini,"pytest"in dependencies - unittest: 内置
Go
*_test.go文件
测试命令
| 语言 | 单元测试 | E2E测试 |
|---|---|---|
| Node.js | npm test |
npx playwright test |
| Python | pytest |
pytest tests/e2e |
| Go | go test ./... |
- |
Playwright E2E 执行细节
完整方法论：详见
Skill(skill: "qa/e2e-playwright")
检测 Playwright 项目
检查以下标志确认项目使用 Playwright：
playwright.config.ts或playwright.config.js存在package.json中包含@playwright/test依赖e2e/或tests/e2e/目录存在
执行命令
# 安装浏览器（首次或 CI 环境）
npx playwright install --with-deps
# 运行全部 E2E 测试
npx playwright test
# 仅 critical 标签（门禁加速）
npx playwright test --grep @critical
# 指定浏览器
npx playwright test --project=chromium
# JSON 报告（门禁解析用）
npx playwright test --reporter=json结果解析
Playwright JSON 报告关键字段：
| 字段 | 说明 |
|---|---|
stats.expected |
通过的测试数 |
stats.unexpected |
失败的测试数 |
stats.flaky |
重试后通过的测试数 |
stats.skipped |
跳过的测试数 |
失败排查
# 查看 trace（失败时自动生成）
npx playwright show-trace <trace.zip路径>
# 打开 HTML 报告
npx playwright show-report
Decide Fit First
Design Intent
How To Use It
Boundaries And Review