Parser will fail if the name of the test is split over several lines in the test file.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- testing-qa, tooling
Research direction
Start by reproducing the parser failure with a test name split across several lines in the test file, then trace the parser entry point that reads test names. Done means multiline test names are parsed successfully without breaking existing test discovery.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- C++
- Stars
- 2
- Forks
- 9
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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.
More from exercism/cpp-test-runner
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
exercism/cpp-test-runner#102 ·
All issues in exercism/cpp-test-runner
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Opencoarray
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·