More test coverage #13

New issue

Closed

opened 2022-06-29 13:50:27 +00:00 by grumbulon · 1 comment

grumbulon commented

2022-06-29 13:50:27 +00:00

Collaborator

So running the following commands go test -v -coverpkg=./... -coverprofile=profile.cov ./... provide us with only 6.1% test coverage for all of awl currently.

Obviously this is very low so more tests will need to be written which fortunatly we can see better coverage of where we are missing things, check this page that Go generated for a more verbose explaination of where our tests are and are not.

So the tl;dr of the file is logawl and query has 0% coverage and the root directory has a whopping 9% coverage and util has ~6%. Full output

go test -v -coverpkg=./... -coverprofile=profile.cov ./...                         
=== RUN   TestApp
--- PASS: TestApp (0.00s)
=== RUN   TestArgParse
--- PASS: TestArgParse (0.00s)
PASS
coverage: 9.9% of statements in ./...
ok      git.froth.zone/sam/awl  0.002s  coverage: 9.9% of statements in ./...
?       git.froth.zone/sam/awl/logawl   [no test files]
?       git.froth.zone/sam/awl/query    [no test files]
=== RUN   TestIPv4
--- PASS: TestIPv4 (0.00s)
=== RUN   TestIPv6
--- PASS: TestIPv6 (0.00s)
=== RUN   TestNAPTR
--- PASS: TestNAPTR (0.00s)
=== RUN   TestInvalid
--- PASS: TestInvalid (0.00s)
PASS
coverage: 6.1% of statements in ./...
ok      git.froth.zone/sam/awl/util     0.002s  coverage: 6.1% of statements in ./...

As a future proposal we may want to add a pipeline step to update that page with the test coverage and include a link in the repo, maybe.

So running the following commands `go test -v -coverpkg=./... -coverprofile=profile.cov ./... ` provide us with only 6.1% test coverage for all of awl currently. Obviously this is very low so more tests will need to be written which fortunatly we can see better coverage of where we are missing things, check [this page](https://grumbulon.xyz/awl.html) that Go generated for a more verbose explaination of where our tests are and are not. So the tl;dr of the file is logawl and query has 0% coverage and the root directory has a whopping 9% coverage and util has ~6%. Full output ``` go test -v -coverpkg=./... -coverprofile=profile.cov ./... === RUN TestApp --- PASS: TestApp (0.00s) === RUN TestArgParse --- PASS: TestArgParse (0.00s) PASS coverage: 9.9% of statements in ./... ok git.froth.zone/sam/awl 0.002s coverage: 9.9% of statements in ./... ? git.froth.zone/sam/awl/logawl [no test files] ? git.froth.zone/sam/awl/query [no test files] === RUN TestIPv4 --- PASS: TestIPv4 (0.00s) === RUN TestIPv6 --- PASS: TestIPv6 (0.00s) === RUN TestNAPTR --- PASS: TestNAPTR (0.00s) === RUN TestInvalid --- PASS: TestInvalid (0.00s) PASS coverage: 6.1% of statements in ./... ok git.froth.zone/sam/awl/util 0.002s coverage: 6.1% of statements in ./... ``` As a future proposal we may want to add a pipeline step to update that page with the test coverage and include a link in the repo, maybe.