Word Count: Test cases don't include examples from description
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- testing
Research direction
Start by comparing the Word Count description's examples with its canonical-data test cases. Add any missing examples to canonical-data, then check whether the same mismatch occurs in other exercises and verify that each documented example is covered.
Written by the indexing model from the issue text.
Description
The example given in the word count description isn't actually included in the canonical data for it. This leads to issues like https://github.com/exercism/haskell/issues/1057 where the reference implementation doesn't solve the given example.
I think it would be good practice to include all examples if any as test case in canonical-data.
This might apply to other exercises too.
- Dominant language
- Ruby
- Stars
- 362
- Forks
- 566
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 8
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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/problem-specifications
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
exercism/problem-specifications#2686 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
exercism/problem-specifications#2704 · 21 comments · 8 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
exercism/problem-specifications#2153 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
exercism/problem-specifications#2120 · 7 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
exercism/problem-specifications#2108 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
All issues in exercism/problem-specifications
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Bug Ruby Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/sentry-ruby#3228 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
開発用DockerイメージにPlaywrightのシステム依存を追加するPossibly taken @momocus claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
sakazuki-org/sakazuki#1453 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100