Re-work `dg-output` test cases
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 231
- Avg merge
- 19h 55m
- Merged PRs (30d)
- 67
Description
A lot of our execution test cases use dg-output for verification. That's OK if really necessary, but generally somewhat non-standard and fragile (I suppose): does matching \n work when the testing host/target system uses a different concept of line endings? At least the \n should be changed into [\n\r]\+?
I suppose a lot of these tests might be re-written into some assert style, so that the result of the actual execution test already tells between PASS and FAIL, without the additional dg-output step.
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 inventorying the execution test cases that use dg-output and read the existing dg-output matching patterns. Determine which cases can use assert-style verification and define completion as removing unnecessary dg-output checks while preserving reliable PASS/FAIL results across line-ending conventions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100