Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discrepancies in code coverage between irongut/CodeCoverageSummary and PublishCodeCoverageResults@1 #304

Open
paweljankowskicolumbus opened this issue Jun 25, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@paweljankowskicolumbus
Copy link

Bug Report

Code coverage seems to be 0% for some of the projects, while there is coverage almost 100%.

Workflow File

      - name: Test
        run: dotnet test --no-build --verbosity normal --collect:"XPlat Code Coverage" --results-directory ./coverage

      - name: Code Coverage Summary Report
        uses: irongut/[email protected]
        with:
          filename: 'coverage/**/coverage.cobertura.xml'
          badge: true
          format: 'markdown'
          output: 'both'

Expected Behavior

Code coverage summary should not differ depend on CI/CD environment

Additional Context

You can see results on attached screenshots below, Azure Devops shows correct values while CodeCoverageSummary action zeroes it for one project. Also, how branch rate can be 100% while line rate is 0%

ironGut
azureDevops

Copy link

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days.

@github-actions github-actions bot added stale and removed stale labels Sep 24, 2024
Copy link

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days.

@github-actions github-actions bot added stale and removed stale labels Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Needs triage
Development

No branches or pull requests

2 participants