2 comments (2 comments)0 reactions (0 reactions)1 assignee (1 assignee)Rust10,406 stars (10,406 stars)1,391 forks (1,391 forks)batch import
A-lintL-testsT-middlegood first issue
Description
allow, because assert!()s may be in the tested code
Contributor guide
- Tech stack
- rust
- Domain
- testingtooling
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-2 days
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- blocked
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- unclear
- Prerequisites
- Rust basicsClippy development setup
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 20
- Research direction
- This issue requests a new lint to detect test functions (annotated with #[test]) that do not contain any assertions. The current description is brief and mentions 'allow', which may indicate that the lint should be allowed by default. First, verify if the assignment to royrustdev is still active by checking recent comments. If the issue is unblocked, study existing clippy lints for test functions (e.g., in clippy lints/src/tests.rs) to understand the pattern. Then propose a design and discuss with maintainers.