Verify analysis debounce with a timer-driven test

Open Beginner friendly
  • Is something wrong?
#132 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
testing

Research direction

Start by reading the analysis debounce implementation and its existing tests; the issue does not name specific files or test entry points. Add a test using a controllable clock that types rapidly and verifies only one analysis occurs after the debounce period.

Written by the indexing model from the issue text.

Description

The headless probe saw one AnalyzeAsync per idle keystroke; the probe cannot show the timer-based debounce. Add a test with a controllable clock that proves rapid typing gives one analysis.

From the env-box review of PR #127 (H:\work\gdr-design-20261102\reports\te-review-env-box.md).

Dominant language
C#
Stars
0
Forks
0
Avg merge
1h 43m
Merged PRs (30d)
43

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sillsdev/SIL.TextEditing

All issues in sillsdev/SIL.TextEditing

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.