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.

Sign up for GitHub

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

Jump to bottom

Coverage Tracking #540

Open
2 tasks
fabianbs96 opened this issue Nov 29, 2022 · 0 comments
Open
2 tasks

Coverage Tracking #540

fabianbs96 opened this issue Nov 29, 2022 · 0 comments
Labels
enhancement New feature or request testing tooling

Comments

@fabianbs96
Copy link
Member

fabianbs96 commented Nov 29, 2022 •
edited
Loading

Story

Phasar NEEDS test coverage tracking. We should enable the CI to track and upload phasars test coverage to:

  • see how we are progressing overall
  • make it easier for developers to spot coverage holes in their analysis
  • make it easier to judge the impact of a PR/change

Prerequisites

  • issue x

Out Of Scope

  • A isn't part of this

Acceptance Criteria

The following acceptance criteria are defined regarding the result of this story:
Clarify what the final result should be, not how to accomplish it.

  • The test coverage (at least one of line-coverage, branch coverage, bb-coverage) is visible for each CI run
  • Optional: The current test coverage is shown as badge in the readme

Related Stories

  • none

Follow-up Stories

  • none
@fabianbs96 fabianbs96 added tooling enhancement New feature or request testing labels Nov 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request testing tooling
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fabianbs96