Investigate gaps in existing Application Set unit tests (via coverage stats), and open issues for them

[jgwest]

Look through the coverage report and look for (significant) areas of the code that are not thoroughly tested. For each identified issue (or set of related issues), open a new GitHub issue. Re: definition of 'significant', part of this issue is developing an understanding/model for what can currently be considered 'significant' 😄 .

If #64 has merged, you can run make test, otherwise:

go test -race -count=1 -coverprofile=coverage.out `go list ./...`

to generate the coverage.out data.

To use this coverage file, generate an HTML report and open in the browser:

go tool cover -html=coverage.out

[jgwest]

Working on this.

[jgwest]

Done, new issues opened:

Write additional tests for repo_service.go:
#102

Write tests for pkg/utils/util.go:
#100

Write tests for clustereventhandler.go:
#99

Write tests for list.go generator:
#98