stress tests should list the features they need
Open
C-Benchmarks
C-Testing
D-Straightforward
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 171
Description
to avoid noise from features that are outside of the scope of a stress test, we should run them with disabled default features and the list of features they need
Contributor guide
Research direction
Start by locating the repository's stress tests and how their default features are currently enabled. Run the relevant stress-test commands, then verify that each test explicitly lists the features it needs and runs without unrelated default features.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100