Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/rtk-ai/rtk/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Executes test commands and filters output to show only failures and summary. Supports all major test frameworks with intelligent parsing.

Syntax

rtk test <COMMAND...>

Arguments

COMMAND
string[]
required
Full test command to execute (e.g., cargo test, pytest, npm test)

Supported Test Frameworks

Rust - Cargo Test

rtk test cargo test
rtk test cargo test --lib
rtk test cargo nextest run
Detects:
  • Test result summary
  • Failed test names
  • Failure details

Python - Pytest

rtk test pytest
rtk test pytest -v tests/
Detects:
  • Passed/failed/error counts
  • Failed test names
  • Assertion failures

JavaScript - Jest/Vitest

rtk test npm test
rtk test yarn test
rtk test pnpm test
Detects:
  • Test Suites summary
  • Tests summary
  • Failed test names (marked with )

Go - Go Test

rtk test go test ./...
rtk test go test -v
Detects:
  • PASS/FAIL lines
  • Failed test output
  • Coverage summary

Output Format

With Failures

❌ FAILURES:
  FAILED tests::test_addition - assertion failed
  FAILED tests::test_division - panicked at 'divide by zero'
  ... +3 more failures

📊 SUMMARY:
  test result: FAILED. 2 passed; 5 failed; 0 ignored

All Passing

📊 SUMMARY:
  test result: ok. 10 passed; 0 failed; 0 ignored

With Errors

❌ FAILURES:
  ERROR tests::setup - connection refused
  FAILED tests::test_api - timeout

📊 OUTPUT (last 5 lines):
  Running 12 tests
  ERROR: connection refused
  test result: FAILED

Token Savings

90% reduction - only failures and summary shown
rtk test cargo test
# Shows only failed tests + summary

Behavior Details

Failure Detection

RTK detects failures via multiple patterns:
  • Lines containing FAILED, ERROR, FAIL
  • Lines containing , ,
  • Assertion failures and panic messages
  • Test framework-specific markers

Summary Extraction

Extracts key summary lines:
  • test result: (Rust)
  • Tests:, Test Suites: (Jest/Vitest)
  • passed, failed, error counts (Pytest)
  • ok, FAIL lines (Go)

Fallback Behavior

If no framework-specific patterns match:
  • Shows last 5 lines of output
  • Preserves exit code
  • Still provides token reduction

Tee Output Recovery

On failure (exit code ≠ 0), RTK automatically saves full output and prints a hint:
❌ FAILURES:
  ...

[full output: ~/.local/share/rtk/tee/test-abc123.txt]
Read the full output without re-running:
rtk read ~/.local/share/rtk/tee/test-abc123.txt

Exit Codes

Preserves the original test command exit code:
  • 0 - All tests passed
  • 1 - Some tests failed
  • 101 - Compilation error (Rust)
  • Other codes preserved as-is
  • rtk cargo test - Rust-specific test filter (90% savings)
  • rtk vitest run - Vitest-specific filter (99.5% savings)
  • rtk playwright test - Playwright-specific filter (94% savings)
  • rtk pytest - Pytest-specific filter (90% savings)
  • rtk err - Show only errors from any command

Build docs developers (and LLMs) love