AugmentClaude

E2E Test

Run end-to-end tests for claude-tap using pytest.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/e2e-test-liaohch3/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Run claude-tap end-to-end tests with pytest

What this skill does

claude-tap E2E Test

Run this skill after modifying core logic in claude-tap, especially:

  • Proxy handler / SSE reassembly (__init__.py)
  • TraceWriter (JSONL writing, flush behavior)
  • HTML viewer generation (viewer.html, _generate_html_viewer)
  • LiveViewerServer (SSE streaming)
  • Signal handling / graceful shutdown
  • Manual update command / trace cleanup

Steps

  1. Run the full test suite:
uv run pytest tests/test_e2e.py -v --timeout=120

Or run a single test:

uv run pytest tests/test_e2e.py::test_e2e -v           # Full E2E pipeline
uv run pytest tests/test_e2e.py::test_trace_cleanup -v  # Trace cleanup
uv run pytest tests/test_e2e.py::test_startup_does_not_contact_pypi -v  # No startup update network
  1. Read the output. Each test prints PASSED or FAILED.

  2. If tests fail, check:

    • test_e2e fails: Core proxy pipeline issue. Check proxy_handler, _handle_streaming, TraceWriter.write.
    • test_trace_cleanup fails: Manifest logic issue. Check _load_manifest, _cleanup_traces, _register_trace.
    • test_startup_does_not_contact_pypi fails: Startup made an unexpected update-related network request.
    • test_live_viewer_ fails*: Viewer HTML issues. Check viewer.html for preserveDetail chain, updateNavButtons.
    • Timeout: May be a network/port issue, not a claude-tap bug.

Related skills