Testing for proxying, including both TOOLS and DUP_TOOLS
Open
Nobody has claimed this yet.
E-mentor
enhancement
help wanted
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
(Note: this has been edited by the rustup team)
1.24.0 shipped with the ability to run cargo fmt, untested.
1.24.1 will not have that defect.
We need to test to make sure that:
- rustup correctly proxies to all of its core tools rather than the subset currently checked.
- rustup correctly proxies to its
DUP_TOOLSlist.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the existing proxying tests and the definitions or usages of TOOLS and DUP_TOOLS. Extend the test coverage to include every core tool and every tool in DUP_TOOLS, then run the relevant rustup test suite and verify that each command is proxied correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100