request: x test vs x test all etc
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Summary
Essentially documenting the zulip discussion taken from #new members > Linux Distribution @ 💬. We believe a distinction between x test, x test all, and x test <subcategory> would be appreciated, especially with regards to bootstrap tests which may be not very predictable depending on OS, and different contributors with different goals may benefit from only testing a specific subsection of tests.
One such approach would be to error out on a plain x test and give suggestions of different test suites. Another (not necessarily contradictory) approach would be to check prerequisites before running a specific suite.
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
Start with the linked Zulip discussion and the bootstrap x test entry point to understand the proposed distinction between x test, x test all, and x test <subcategory>. Done means agreeing on the test-suite behavior and prerequisite checks, then documenting or implementing the selected approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100