Code Monkey home page Code Monkey logo

codecoverage-yaml-samples's Introduction

Settings for Code Coverage reporting in Azure Pipelines

Azure Pipelines provides code coverage reporting. This experience can be tweaked using a settings YAML file (named azurepipelines-coverage.yml) included at the root of your repo.

Each of the folders in this repo contains a sample file for changing a setting.

File/folder Description
SetDiffCoverageTarget Change the diff coverage threshold for pull requests.
EnableCoverageDetailComments Post details about lines covered/not covered for each code file in a pull request.
DisableCodeCoveragePullRequestStatus Opt out of code coverage pull request capability.

Related docs

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

codecoverage-yaml-samples's People

Contributors

boraprachi avatar microsoftopensource avatar msftgits avatar pboramsft avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

codecoverage-yaml-samples's Issues

Set different diff code coverage for different files

Hi all,
Is there any way to set different target for different files? We have different requirements for each file.
By the way, where can I find the docs of all supported params in azurepipelines-coverage.yml?

Diff code coverage targets of different tiers

The ability to set custom diff coverage targets based on the number of lines changed.
e.g.,
coverage:
-- status:
---- diff:
------ target: 75%
------ custom:
-------- changedLineCountNoMoreThan: 2
-------- target: 50%

Thanks.

Location of azurepipelines-coverage.yml

Hi,

Is it mandatory to have azurepipelines-coverage.yml at the root of the repo? In my case, I have organized my yaml files under

<proj_root>\AzurePipelines
Development\azure-pipeline.yml
ReleaseR1.0.0\azure-pipeline.yml

and so on.

It is my suggestion that azurepipelines-coverage.yml should be placed alongside the main yaml for the build pipeline that is configured for the pull request.

Now, I will be forced to keep it as a lone .yml file in the project root.

Am I missing something?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.