Test

by parcadeid07ff4b06b62No license3.9K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 8 months ago

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

Instructions onlySoftware Development
AI-generated overview

Runs a staged software test workflow: type diagnostics, parallel unit and integration tests, then E2E tests.

What it does
This skill defines a testing workflow that starts with pre-flight type diagnostics, then runs unit tests, type checks and linting in parallel with integration and API tests, and finally runs end-to-end and acceptance tests only if the earlier phases pass. It reports pass/fail counts and failure details, and can optionally narrow the run to tests affected by recent changes. It also describes flags for quick unit-only runs, skipping E2E, coverage reports and watch mode.
When to use it
Use it when asked to run all tests, test a feature, verify everything works, or run a full test suite, especially before releases or merges and after major changes.
Requirements
Instructions only; no scripts are shipped. It expects a test runner and the tldr diagnostics and change-impact commands, plus subagents named arbiter and atlas for the parallel and sequential phases.

/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

Source and attribution

Source:parcadei/continuous-claude-v3in.claude/skills/testat commitd07ff4b

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from parcadei/continuous-claude-v3

Tldr Stats

parcadei

Displays a dashboard of session token usage, API costs, TLDR compression savings, and hook activity.

Data & Analytics3.9Kupdated 8 months ago

Wiring

parcadei

Guides verification that built infrastructure components are actually invoked in the execution path, not left as dead code.

Software Development3.9Kupdated 8 months ago

Workflow Router

parcadei

Routes a user's goal to specialist agents and resource levels for research, planning, building, or fixing tasks.

AI & Agents3.9Kupdated 8 months ago

Validate Agent

parcadei

Validates a technical plan's technology choices against current best practices and writes a validation handoff.

Software Development3.9Kupdated 8 months ago

Tour

parcadei

Provides a friendly onboarding overview of an agent's capabilities when users ask what it can do.

AI & Agents3.9Kupdated 8 months ago

Tldr Overview

parcadei

Produces a token-efficient overview of an unfamiliar codebase using the TLDR stack's tree, structure, call graph and complexity commands.

Software Development3.9Kupdated 8 months ago

More in Software Development

Playground

anthropics

Featured

Builds self-contained interactive HTML playgrounds with controls, live preview, and copyable prompt output.

Software Development37Kupdated today

M5 Onboard

anthropics

Featured

Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.

Software Development37Kupdated today

Cardputer Buddy

anthropics

Featured

Guides iterating on a Cardputer-Adv MicroPython app bundle: adding apps, pushing files over USB-serial, tailing logs, and running REPL commands.

Software Development37Kupdated today

Web Design Guidelines

vercel-labs

Featured

Reviews UI code against Web Interface Guidelines fetched from a remote source and reports findings as file:line entries.

Software Development32Kupdated 5 weeks ago

Vercel React Native Skills

vercel-labs

Featured

React Native and Expo best-practice rules covering list performance, animation, navigation, UI patterns, state, and monorepo setup.

Software Development32Kupdated 5 weeks ago

Vercel React Best Practices

vercel-labs

Featured

Vercel's React and Next.js performance guidelines, organized as 70 rules for writing, reviewing, and refactoring code.

Software Development32Kupdated 5 weeks ago