kubernetes / kubernetes/perf-tests
clusterloader2 should be covered with unit tests
Open
area/clusterloader
good first issue
help wanted
kind/cleanup
lifecycle/frozen
- Dominant language
- Go
- Stars
- 989
- Forks
- 654
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 56
Description
Currently clusterloader2 has not tests at all. Testing new functionality requires spinning up a new cluster and running newly added code against it. It's costly and feedback loop is slow.
Contributor guide
Research direction
Start by locating the clusterloader2 entry point and mapping its existing functionality before deciding what can be tested in isolation. Add unit-test coverage so new functionality can be exercised without spinning up a cluster, and verify that the tests provide a faster feedback loop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100