Builtin coverage

[ahasikos]

Description

Increases test coverage of the builtin package and specifically:

• authority.go
• gen/bindata.go

Fixes #190

Type of change

Adds code coverage tests

How Has This Been Tested?

make test

Test Configuration:

• Go Version: go1.22.1 darwin/arm64
• Hardware: MBP M3
• Docker Version: -

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] New and existing E2E tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules
• [x] I have not added any vulnerable dependencies to my code

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 61.67%. Comparing base (4fa7366) to head (169b35f). Report is 6 commits behind head on master.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #736 +/- ## ========================================== + Coverage 61.36% 61.67% +0.31% ========================================== Files 194 195 +1 Lines 18223 18246 +23 ========================================== + Hits 11182 11253 +71 + Misses 5959 5897 -62 - Partials 1082 1096 +14 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[ahasikos]

@paologalligit I agree. We need to decide on how we exclude either functions or files from being tested.

[libotony]

@paologalligit I agree. We need to decide on how we exclude either functions or files from being tested.

Could you remove the generated file's test and let's find a way to improve the codecov strategy?