Skip to content

Unexpected branches reported for async lambda expression #584

@MarcoRossignoli

Description

@MarcoRossignoli

In PR #583 we fixed the issue with false line coverage for lambda.
Now we report a correct line coverage, but we've unexpected uncovered branches reported.
We should try to avoid to report compiler generated branches.
Test name Lambda_Issue343

Capture

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementGeneral enhancement requesttenet-coverageIssue related to possible incorrect coverageup-for-grabsGood issue for contributors

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions