redhat-et / redhat-et/docsclaw
chore: add unit tests for dashboard utilities
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 1
- Avg merge
- 6h 9m
- Merged PRs (30d)
- 1
Description
From PR #66 review (GLM 5.1, findings #19-20):
The dashboard package has no test files. Add unit tests for:
ParseTokensFromLogs— various log formats, empty inputparseMemory/parseCPU— edge cases: Ki, Mi, Gi, n, m, bare numbersextractArtifactText— a2a-go v2 response formatcleanHRReport— JSON stripping, document ID extraction
These are pure functions with no external dependencies, easy to test.
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.
Research direction
Start by locating ParseTokensFromLogs, parseMemory, parseCPU, extractArtifactText, and cleanHRReport in the dashboard package, then inspect their signatures and existing package layout. Add unit tests covering the listed formats and edge cases, and run the dashboard package tests; done means each pure function has coverage for the requested inputs and the tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100