Improve unit testing coverage in Fetcher.go
Open
area/testing
kind/cleanup
team/cli
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What would you like to be added**:
Unit test coverage is currently significantly lacking in the public methods under fetcher.go, as discussed in https://github.com/aws/eks-anywhere/pull/1577. We need to add tests for the currently untested methods
**Why is this needed**:
Adding unit tests is good practice to avoid unintentional regressions
Contributor guide
Research direction
Start by reading fetcher.go and the discussion in pull request #1577 to identify the public methods that lack coverage. Add unit tests for those methods, then run the relevant Go package tests and confirm the untested public methods are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100