Skip to content

Better Test coverage #138

Closed
5 of 5 issues completed
Closed

Description

@yeoldegrove

What would you like to be added:

Not all of our functions have a valid unit test.
We need to way to make this visible.

Why is this needed:

Be more confident that the code does what it is supposed to do. Make breaking changes visible.

Activity

  1. added this to the 2025-07 milestone on Jul 14, 2025
  2. modified the milestones: 2025-07, 2025-08 on Aug 1, 2025
  3. ByteOtter commented on Aug 7, 2025

    @ByteOtter
    Contributor

    Latest commits have thrown our test coverage aback to below the 70% mark. Some modules are not covered at all.
    I would like to take care of this next to bring it up to at least 85% again and adjust the reporting workflow accordingly to fail below 80%, rather than 50%.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions