Tracking Issue for UI test suite subdirectory summary
Open
Nobody has claimed this yet.
A-testsuite
C-tracking-issue
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Idea is to have a top-level tests/ui/SUMMARY.md briefly outlining subdirectories and their purpose in the ui test suite.
As part of #gsoc > Project: Mapping the Maze of Rust's UI Test Suite.
Implementation history
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 by reviewing tests/ui and the implementation history in PR #141597. The work is done when tests/ui/SUMMARY.md briefly identifies the UI test suite's subdirectories and explains each directory's purpose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100