Skip to content

Yeti with Istanbul code coverage reports on jasmine tests #82

Description

@AniruddhBhatt1

The coverage reports generated are sometimes not consistent. I ran my SPA using Yeti on nodejs command prompt on jamine framework testing a SPA and I configured the coverage option on .yeti.json file once for getting html report & once for lcov report(like below). I got the following code coverage like below:

image
image

Html report:
image

Lcov report:
image

The function(& statement) was not covered inlcov report giving me a different coverage stat. On the next test run it was fixed and the function was covered . This problem also happens the other way around(html having problem).

When I tested this for consistency about 50 test runs each(html & Lcov) I got that test coverage problem twice for both. So Html coverage error freq was about 4.25% and lcov coverage error freq was 3.77%.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    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