rust-lang / rust-lang/rust-bindgen
Consider using `assert_cmd` for testing
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
The assert_cmd crate can be used to test CLI tools (like bindgen!) and compare not only their output but also the stderr, exit status and whatnot.
I think we could consider using this to remove some ad-hoc logic from bindgen-tests and hopefully be able to test the diagnostic messages we're working on.
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 reading the assert_cmd documentation and locating the existing ad-hoc test logic in bindgen-tests. Replace the relevant CLI-testing logic with assert_cmd usage, preserving checks for output, stderr, and exit status, and confirm that diagnostic messages can be tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100