Add tests for Formatting.Countdown and Formatting.Ago
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 90/100
Research direction
Read src/GilSweep.Core/Formatting.cs and its doc comments, then add cases to tests/GilSweep.Tests/Core/FormattingTests.cs for the listed Countdown and Ago boundaries. Pass TimeSpan values directly, and run dotnet test --project tests/GilSweep.Tests; done means every listed boundary is covered and the test command passes.
Written by the indexing model from the issue text.
Description
Countdown (node timers: "7m 32s", "1h 05m") and Ago (sweep freshness: "4 min ago") in src/GilSweep.Core/Formatting.cs have no tests. Their doc comments give the rules; the edges are where bugs hide.
To do: add cases to tests/GilSweep.Tests/Core/FormattingTests.cs (create it if needed):
Countdown: 0 s, 59 s, 3,599.4 s ("59m 59s"), 3,599.6 s ("1h 00m"), 3,725 s ("1h 02m"), and a negative time ("0m 00s").Ago: 59 s ("just now"), 60 s, 59 min, 1 h, 47 h 59 min, and 48 h ("2 days ago").
Pass TimeSpan values directly; no clock is needed. If a result looks wrong, say so here rather than changing the code in the same PR.
Done when each boundary above is covered and dotnet test --project tests/GilSweep.Tests passes.
- Dominant language
- C#
- Stars
- 0
- Forks
- 1
- Avg merge
- 23m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No 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 hazeliscoding/gil-sweep
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hazeliscoding/gil-sweep#25 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement later
Difficulty 4/5 3-5 days Newbie friendliness 35/100
hazeliscoding/gil-sweep#40 ·
Maintainers usually reply within 1 day
-
enhancement later
Difficulty 5/5 Over a week Newbie friendliness 35/100
hazeliscoding/gil-sweep#39 ·
Maintainers usually reply within 1 day
-
A winget packageOpenenhancement later
Difficulty 4/5 3-5 days Newbie friendliness 48/100
hazeliscoding/gil-sweep#38 ·
Maintainers usually reply within 1 day
All issues in hazeliscoding/gil-sweep
Similar issues
-
devtools
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr clawsweeper:not-repro-on-main impact:ux-release-blocker issue-rating: 🦪 silver shellfish P0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openclaw/openclaw-windows-node#1843 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
kind:ux size:S type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
elsa-workflows/elsa-foundation#3256 ·
Maintainers usually reply within 1 day
-
[Bug]: Revit selector reads process ids 2000-2099 as years (flaky AgentClientTests.AYearOrAProcessIdSelectsTheHost)Possibly taken @Wurschdhaud claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
pyrevitlabs/pyRevit#3817 ·
Maintainers usually reply within 1 day