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

Test Coverage #552

Open
ndcgundlach opened this issue Jun 28, 2022 · 3 comments
Open

Test Coverage #552

ndcgundlach opened this issue Jun 28, 2022 · 3 comments
Labels
planning Propose change to milestone in next planning meeting

Comments

@ndcgundlach
Copy link
Contributor

We need to measure test coverage for both unit and integration tests.

@vladtr vladtr moved this to Todo in ENF Engineering Jul 1, 2022
@arhag arhag added the planning Propose change to milestone in next planning meeting label Jul 21, 2022
@stephenpdeos
Copy link
Member

Previously, there were code coverage reports that would be generated as part of the CICD process.

We need a step in the CI that generates a report similar to what was in the historical EOSIO repo.

@ndcgundlach could you add a couple more details to help us refine this?

@stephenpdeos
Copy link
Member

Also, can we illustrate use cases for the support? We want to make sure this coverage report triggers actionable next steps. Thanks!

@stephenpdeos
Copy link
Member

Action item: @heifner to grab time with Alysha to identify process opportunities to justify this work (e.g. blocking steps based off coverage, dashboard health metrics)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
planning Propose change to milestone in next planning meeting
Projects
Status: Todo
Development

No branches or pull requests

3 participants