Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report coverage for tests #1784

Open
LucaGuerra opened this issue Apr 8, 2024 · 0 comments
Open

Report coverage for tests #1784

LucaGuerra opened this issue Apr 8, 2024 · 0 comments
Labels
kind/feature New feature or request

Comments

@LucaGuerra
Copy link
Contributor

LucaGuerra commented Apr 8, 2024

Motivation

In the last 1~2 years we have improved test suites and coverage by a lot. If you look at libsinsp unit testing alone we went from about 6% to ~70% of the library. In addition we have the Python e2e suite and the recent C++ e2e suite, plus all driver tests that exercise single syscalls. The amount of coverage we get from all those should be maintained going forward so we should measure it and report it on PRs for each large test suite.

How to properly measure that in a way that is not misleading may be tricky and require experimentation

Alternatives

Leave it unreported. People will still add tests but maybe sometimes we won't have full context.

Additional context

@LucaGuerra LucaGuerra added the kind/feature New feature or request label Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant