Skip to content

.NET Standard 1.x + async - Wrong branch coverage #1376

New issue
New issue
Closed
#1433
Closed
.NET Standard 1.x + async - Wrong branch coverage#1376
#1433
Labels
bugSomething isn't workingtenet-coverageIssue related to possible incorrect coverage
@vers-one

Description

@vers-one
vers-one
opened on Aug 30, 2022

I think this is the same issue as #113 but affecting only .NET Standard 1.x projects. (Unfortunately, I have to use .NET Standard 1.3 in my project.)

Reproduction: https://github.com/vers-one/AsyncCoverageIssue

Coverage report:
CoverageReport

Projects targeting .NET or even .NET Standard 2.x don't exhibit this issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtenet-coverageIssue related to possible incorrect coverage

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy