Skip to content

Missing coverage information in generic format #1666

@chrisberkhout

Description

@chrisberkhout

The problem

Using --coverage-format=generic produces an XML report that is missing the coverage that is expected, and that is correctly reported when using --coverage-format=cobertura.

An example

This command:

elastic-package test pipeline -v --test-coverage --coverage-format=cobertura

when run for example on elastic/integrations#9077, will produce expected coverage numbers, like this:

| Filename                                                                         |   Stmts |   Miss |
|----------------------------------------------------------------------------------|---------|--------|
| packages/zoom/data_stream/webhook/elasticsearch/ingest_pipeline/account.yml      |      95 |     25 |
| packages/zoom/data_stream/webhook/elasticsearch/ingest_pipeline/chat_channel.yml |      53 |      7 |
| packages/zoom/data_stream/webhook/elasticsearch/ingest_pipeline/chat_message.yml |      48 |     15 |
| packages/zoom/data_stream/webhook/elasticsearch/ingest_pipeline/default.yml      |     102 |      0 |
| packages/zoom/data_stream/webhook/elasticsearch/ingest_pipeline/meeting.yml      |     152 |     16 |
| packages/zoom/data_stream/webhook/elasticsearch/ingest_pipeline/phone.yml        |     155 |      9 |
| packages/zoom/data_stream/webhook/elasticsearch/ingest_pipeline/recording.yml    |     105 |     10 |
| packages/zoom/data_stream/webhook/elasticsearch/ingest_pipeline/user.yml         |     162 |     19 |
| packages/zoom/data_stream/webhook/elasticsearch/ingest_pipeline/webinar.yml      |     118 |      0 |
| packages/zoom/data_stream/webhook/elasticsearch/ingest_pipeline/zoomroom.yml     |      16 |      4 |
| TOTAL                                                                            |    1006 |    105 |

But when the generic format is used as follows:

elastic-package test pipeline -v --test-coverage --coverage-format=generic

The report will only show coverage for default.yml and account.yml. That's causing SonarQube Quality Gate failures.

Related issues

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions