elastic / elastic/elastic-package

[tests] Expand coverage results

Open
#2,704 1 comment 1 reaction 0 assignees View on GitHub
good first issue Team:Ecosystem
Dominant language
Go
Stars
72
Forks
141
Avg merge
19h 42m
Merged PRs (30d)
55

Description

Following paths are not covered in the coverage reports for each ``:

```
./data_stream/*/lifecycle.yml
./data_stream/*/elasticsearch/ilm/*
./elasticsearch/transform/*
./kibana/tags.yml
./kibana/tag/*
./validation.yml
```

This leads to low coverage of packages inside PRs and scheduled CI runs.
Example: https://github.com/elastic/integrations/pull/14290#issuecomment-2998896369 which has 18% coverage on new code.

Increase coverage on these paths. Alternately add these paths into [exclusion list](https://github.com/elastic/integrations/blob/main/sonar-project.properties#L10) as temporary measure.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with sonar-project.properties, especially the exclusion list linked in the issue, and inspect how coverage reports are produced for the listed data_stream, elasticsearch, kibana, and validation.yml paths. Confirm the current behavior in a PR or scheduled CI coverage run. Done means those paths are either represented in coverage results or intentionally excluded, with the resulting coverage no longer misleading.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
ci-cd, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.