Test

作者 parcadeid07ff4b06b62无许可证3.9K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库8个月前更新

Comprehensive testing workflow - unit tests ∥ integration tests → E2E tests

仅含说明Software Development
AI 生成的概览

运行分阶段的软件测试流程：类型诊断、并行的单元与集成测试，然后是端到端测试。

功能
该技能定义了一套测试流程：先进行预检类型诊断，然后并行运行单元测试、类型检查和代码检查，以及集成测试和 API 测试，只有在前面阶段通过后才运行端到端和验收测试。它会报告通过/失败数量及失败详情，并可选择只运行受近期改动影响的测试。它还说明了快速仅单元测试、跳过端到端测试、覆盖率报告和监视模式等标志。
适用场景
当被要求运行所有测试、测试某个功能、验证一切是否正常或运行完整测试套件时使用，尤其适用于发布或合并之前以及重大改动之后。
运行要求
仅为说明文档，不附带脚本。它需要测试运行器以及 tldr diagnostics 和 change-impact 命令，还需要名为 arbiter 和 atlas 的子代理来执行并行和顺序阶段。

/test - Testing Workflow

Run comprehensive test suite with parallel execution.

When to Use

  • "Run all tests"
  • "Test the feature"
  • "Verify everything works"
  • "Full test suite"
  • Before releases or merges
  • After major changes

Workflow Overview

┌─────────────┐      ┌───────────┐│ diagnostics │ ──▶  │ arbiter  │ ─┐│ (type check)│      │ (unit)    │  │└─────────────┘      └───────────┘  │                                    ├──▶ ┌─────────┐                     ┌───────────┐  │    │  atlas  │                     │  arbiter  │ ─┘    │ (e2e)   │                     │ (integ)   │       └─────────┘                     └───────────┘
  Pre-flight         Parallel              Sequential  (~1 second)        fast tests            slow tests

Agent Sequence

#AgentRoleExecution
1arbiterUnit tests, type checks, lintingParallel
1arbiterIntegration testsParallel
2atlasE2E/acceptance testsAfter 1 passes

Why This Order?

  1. Fast feedback: Unit tests fail fast
  2. Parallel efficiency: No dependency between unit and integration
  3. E2E gating: Only run slow E2E tests if faster tests pass

Execution

Phase 0: Pre-flight Diagnostics (NEW)

Before running tests, check for type errors - they often cause test failures:

bash
tldr diagnostics . --project --format text 2>/dev/null | grep "^E " | head -10

Why diagnostics first?

  • Type check is instant (~1s), tests take longer
  • Diagnostics show ROOT CAUSE, tests show symptoms
  • "Expected int, got str" is clearer than "AttributeError at line 50"
  • Catches errors in untested code paths

If errors found: Fix them BEFORE running tests. Type errors usually mean tests will fail anyway.

If clean: Proceed to Phase 1.

Phase 0.5: Change Impact (Optional)

For large test suites, find only affected tests:

bash
tldr change-impact --session# or for explicit files:tldr change-impact src/changed_file.py

This returns which tests to run based on what changed. Skip this for small projects or when you want full coverage.

Phase 1: Parallel Tests

# Run both in parallelTask(  subagent_type="arbiter",  prompt="""  Run unit tests for: [SCOPE]
  Include:  - Unit tests  - Type checking  - Linting
  Report: Pass/fail count, failures detail  """,  run_in_background=true)
Task(  subagent_type="arbiter",  prompt="""  Run integration tests for: [SCOPE]
  Include:  - Integration tests  - API tests  - Database tests
  Report: Pass/fail count, failures detail  """,  run_in_background=true)
# Wait for both[Check TaskOutput for both]

Phase 2: E2E Tests (If Phase 1 Passes)

Task(  subagent_type="atlas",  prompt="""  Run E2E tests for: [SCOPE]
  Include:  - End-to-end flows  - Acceptance tests  - UI tests if applicable
  Report: Pass/fail count, screenshots on failure  """)

Test Scopes

Full Suite

User: /test→ All unit + integration + E2E tests

Feature Scope

User: /test authentication→ Only auth-related tests

Quick Check

User: /test --quick→ Only unit tests (skip integration and E2E)

Example

User: /test the new payment feature
Claude: Starting /test workflow for payment feature...
Phase 0: Pre-flight diagnostics...$ tldr diagnostics . --project --format text | grep "^E "(no type errors found)
Phase 1: Running parallel tests...┌─────────────────────────────────────────┐│ arbiter: Running unit tests...          ││ arbiter: Running integration tests...   │└─────────────────────────────────────────┘
arbiter: ✅ 45/45 unit tests passingarbiter: ✅ 12/12 integration tests passing
Phase 2: Running E2E tests...atlas: ✅ 8/8 E2E tests passing
Test Summary:┌─────────────┬─────────┬────────┐│ Type        │ Passed  │ Failed │├─────────────┼─────────┼────────┤│ Unit        │ 45      │ 0      ││ Integration │ 12      │ 0      ││ E2E         │ 8       │ 0      │├─────────────┼─────────┼────────┤│ TOTAL       │ 65      │ 0      │└─────────────┴─────────┴────────┘
All tests passing! ✅

Example with Type Errors

User: /test
Claude: Starting /test workflow...
Phase 0: Pre-flight diagnostics...$ tldr diagnostics . --project --format text | grep "^E "E src/payment.py:45:12: Argument of type 'str' not assignable to 'int'E src/refund.py:23:8: Return type 'None' not assignable to 'float'
Found 2 type errors. Fixing before running tests...
[Claude fixes the type errors]
Re-running diagnostics... clean.
Phase 1: Running parallel tests...

Failure Handling

If Phase 1 fails:

arbiter: ❌ 43/45 tests passing
2 failures:- test_payment_validation: expected 'invalid' got 'valid'- test_refund_calculation: off by $0.01
Stopping workflow. Fix failures before running E2E tests.

Flags

  • --quick: Unit tests only
  • --no-e2e: Skip E2E tests
  • --coverage: Include coverage report
  • --watch: Re-run on file changes

来源与署名

来源：parcadei/continuous-claude-v3位于.claude/skills/test提交d07ff4b

许可证： 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

更多来自 parcadei/continuous-claude-v3 的技能

Tldr Stats

parcadei

展示会话 token 用量、API 费用、TLDR 压缩节省额以及 hook 活动情况的仪表盘。

Data & Analytics3.9K8个月前更新

Wiring

parcadei

指导验证已构建的基础设施组件是否真正被调用，而非成为死代码。

Software Development3.9K8个月前更新

Workflow Router

parcadei

将用户目标路由到相应的专家代理和资源级别，用于研究、规划、构建或修复任务。

AI & Agents3.9K8个月前更新

Validate Agent

parcadei

根据当前最佳实践验证技术方案中的技术选型，并生成验证交接文档。

Software Development3.9K8个月前更新

Tour

parcadei

当用户询问能力时，提供友好的入门介绍，概述智能体可以做什么。

AI & Agents3.9K8个月前更新

Tldr Overview

parcadei

使用 TLDR 工具链生成节省 token 的项目概览，涵盖文件树、代码结构、调用图与复杂度。

Software Development3.9K8个月前更新

更多Software Development技能

Playground

anthropics

精选

构建自包含的交互式 HTML 演练场，包含控件、实时预览和可复制的提示词输出。

Software Development37K今天更新

M5 Onboard

anthropics

精选

通过 USB 检测 M5Stack ESP32 开发板，刷写 UIFlow 2.0 固件并安装 MicroPython 应用包。

Software Development37K今天更新

Cardputer Buddy

anthropics

精选

指导迭代 Cardputer-Adv 的 MicroPython 应用包：添加应用、通过 USB 串口推送文件、查看日志并运行 REPL 命令。

Software Development37K今天更新

Web Design Guidelines

vercel-labs

精选

依据从远程来源获取的 Web Interface Guidelines 审查 UI 代码，并以 file:line 形式报告问题。

Software Development32K5周前更新

Vercel React Native Skills

vercel-labs

精选

React Native 与 Expo 最佳实践规则，涵盖列表性能、动画、导航、UI 模式、状态与 monorepo 配置。

Software Development32K5周前更新

Vercel React Best Practices

vercel-labs

精选

Vercel 的 React 与 Next.js 性能指南，以 70 条规则的形式用于编写、审查和重构代码。

Software Development32K5周前更新