Somehow prevent test.run scripts from referring to the wrong binary
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
For the second time, I found a .run file that was invoking the wrong binary. That costs us regression coverage. I don't have any great ideas, but making the common-case .run link to a generic version that infers the binary name from the .run filename might work.
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 the existing .run files and how they invoke binaries. Determine a convention that prevents a .run file from referring to the wrong binary; done means regression coverage is no longer silently lost from incorrect binary references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100