rtk-ai/rtk

pytest collection fails with no-args invocation

Open

#1417 opened on Apr 20, 2026

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
bugeffort-smallfilter-qualitygood first issue

Description

The problem is rtk pytest with no args — that returned "No tests collected" while rtk pytest tests/test_cli_dispatch.py -v worked. There's an rtk bug in how it handles the no-args pytest invocation, probably in its cwd handling or in how it discovers tests when the path isn't explicit.

Contributor guide

Tech stack
rust
Domain
clideveloper experience
Issue type
bug
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.
1-3 hours
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.
mostly clear
Prerequisites
Rust programming basicsCLI argument parsingUnderstanding of test discovery
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the argument parsing logic for the 'pytest' subcommand, specifically the handling when no test path is provided. Look at the code that sets the default working directory or test discovery path. Focus on the cwd handling functions and any logic that determines whether to pass an explicit path or rely on automatic discovery. Check if there are existing tests for the pytest subcommand and consider adding a test for the no args case.