Skip to content

AzureDevOpsDsc: Increase unit test, code coverage #22

@SphenicPaul

Description

@SphenicPaul

Details of the scenario you tried and the problem that is occurring

Test coverage threshold in the build.yml file is currently set to 40 (%) to allow initial builds to execute/succeed - Although a number of classes within the unit tests are covered, Pester is not recognising the coverage.

This needs investigating and may require a refactoring of tests and/or classes (also note #10 relating to classes within the module).

Ideally, attempt to set code coverage threshold to 100% or 95%.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Backlog - Mid TermBacklog - Mid Termhelp wantedThe issue is up for grabs for anyone in the community.testsThe issue or pull request is about tests only.

    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