Test real Codex CLI sessions through claude-tap, including resumed conversations, multiple tool calls, and image input. Check captured API activity and viewer behavior, then collect screenshots as evidence for a pull request.
- Validate API capture and proxy changes
- Test resumed conversations with image input
- Check message rendering and tool call order
liaohch3/claude-tap☆ 3.3KUpdated Oct 22, 2026
Run pytest tests for claude-tap after core changes to check the workflow from end to end. Review results for proxy processing, trace storage, cleanup, and viewers, with guidance on where to investigate failures.
- Check the full workflow after proxy changes
- Verify trace cleanup behavior
- Check that startup avoids update network requests
liaohch3/claude-tap☆ 3.3KUpdated Oct 22, 2026
Test JavaScript embedded in HTML with two complementary layers: Python unit tests for algorithms and Playwright browser tests for page behavior. Check calculations, button states, keyboard input, and navigation using prepared test data.
- Checking algorithms embedded in HTML
- Testing button states and overlay visibility
- Verifying keyboard and click navigation
liaohch3/claude-tap☆ 3.3KUpdated Oct 22, 2026
Check maintainer documentation locally before automated CI checks run. Find missing metadata, outdated review dates, nonexistent paths in the architecture manifest, and completed plans that still contain unfinished tasks, with guidance for correcting common failures.
- Check required metadata after updating standards
- Find outdated review dates
- Verify paths listed in the architecture manifest
liaohch3/claude-tap☆ 3.3KUpdated Oct 22, 2026
Record Playwright browser test actions as .webm videos for pull request reviews, bug fix comparisons, and regression evidence. Combine readable pauses, assertions, and terminal logs to show interface behavior alongside automated checks.
- Recording before-and-after behavior for a bug fix
- Sharing interface changes in a pull request review
- Saving video evidence of regression test paths
liaohch3/claude-tap☆ 3.3KUpdated Oct 22, 2026
Check whether a pull request is ready to merge by combining local lint, formatting, and tests with GitHub Actions status and PR description requirements. Returns a readiness verdict with specific reasons for any failed checks.
- Running local checks before opening a pull request
- Reviewing an existing pull request’s merge readiness
- Finding failing or pending GitHub Actions checks
liaohch3/claude-tap☆ 3.3KUpdated Oct 22, 2026