Skip to content

Increase coverage so the lib can make the 'awesome-go' list #29

@kpacha

Description

@kpacha

We've lost some of the coverage earned at #6 but we were not close to the requirements of https://github.com/avelino/awesome-go/blob/master/CONTRIBUTING.md#quality-standards

Tests, where practical. If the library/program is testable, then coverage should be >= 80% for non-data-related packages and >=90% for data related packages. Notice: the tests will be reviewed too. We will check your coverage manually if your package's coverage is just a benchmark results.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions