Lexicon: add tests for correction rules
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- testing
Research direction
The issue names no file, function or test, so start by locating the lexicon/correction module and any tests that already exist for it. Write tests for the four listed areas: exact replacements, case-sensitive protected words, overlap and ordering, and tricky-name regressions. Done when each area has at least one passing test that pins the current behavior, and the expected outputs for ordering and overlap are confirmed with a maintainer first.
Written by the indexing model from the issue text.
Description
Add automated tests for the lexicon / correction system.
Scope:
- exact replacement cases
- case-sensitive protected words
- overlap / ordering behavior
- regression coverage for tricky names
Goal:
Make the correction engine safe to evolve.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- Avg merge
- 16m
- Merged PRs (30d)
- 40
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from graygarbage/HermesKey
-
enhancement ux
Difficulty 4/5 3-5 days Newbie friendliness 25/100
graygarbage/HermesKey#16 ·
Maintainers usually reply within 1 day
-
enhancement packaging
Difficulty 3/5 Half a day Newbie friendliness 40/100
graygarbage/HermesKey#15 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement packaging
Difficulty 4/5 3-5 days Newbie friendliness 32/100
graygarbage/HermesKey#14 ·
Maintainers usually reply within 1 day
-
enhancement packaging
Difficulty 3/5 1-2 days Newbie friendliness 50/100
graygarbage/HermesKey#13 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement gui lexicon
Difficulty 4/5 3-5 days Newbie friendliness 30/100
graygarbage/HermesKey#12 ·
Maintainers usually reply within 1 day
All issues in graygarbage/HermesKey
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
good first issue packaging
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
area:docs visibility
Difficulty 1/5 Under an hour Newbie friendliness 85/100
reacher-z/Awesome-CUA#336 ·
Maintainers usually reply within 1 day