rtk-ai/rtk

feat: add bats/TAP test runner filter

Open

#1,908 opened on May 16, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (2,914 forks)batch import
area:clienhancementhelp wantedpriority:medium

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

Problem

bats (Bash Automated Testing System) outputs TAP (Test Anything Protocol) format. It is the highest-volume unhandled command in real-world Claude Code sessions — 353 calls/month per rtk discover --all across 1,178 sessions and 15,483 Bash commands. Currently passes through unfiltered.

TAP Output Format

1..5
ok 1 - test basic install
ok 2 - test git config
not ok 3 - test brew install
# (from function `assert' in file test_helper.bash, line 12)
#   `assert_success' failed
ok 4 - test skills deploy
ok 5 - test status

Proposed Filter

  • Strip blank lines and bare # comment lines (noise on passing tests)
  • Preserve TAP plan (1..N), passing ok lines, and all failure details (including # context lines)
  • max_lines = 60 to cap runaway output on large suites
  • on_empty = "bats: ok" for empty output

Expected Token Savings

~75% on typical passing runs (blank-line noise removed). Failure output preserved in full — critical for Claude to understand what broke.

Contributor guide

Research direction
Implement the TAP filter in Rust. Study existing filters for other tools (e.g., pytest, cargo) to follow the pattern. Add unit tests for the filter logic.
Tech stack
rust
Domain
testing
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70