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

[Feature]: Add Code coverage results to the crypto binary #68

Closed
kenlautner opened this issue Feb 14, 2024 · 2 comments · Fixed by #104
Closed

[Feature]: Add Code coverage results to the crypto binary #68

kenlautner opened this issue Feb 14, 2024 · 2 comments · Fixed by #104
Assignees
Labels
state:backlog In the backlog state:needs-triage Needs to triaged to determine next steps state:stale Has not been updated in a long time type:feature-request A new feature proposal urgency:high Significant with a critical impact

Comments

@kenlautner
Copy link
Contributor

Feature Overview

With Crypto being such a critical path in firmware it makes sense to add code coverage to the binary. This will provide the benefit of confidence in our binaries functionality.

Solution Overview

Add code coverage testing and results to the binary build pipeline.

Alternatives Considered

No response

Urgency

High

Are you going to implement the feature request?

I will implement the feature

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

@kenlautner kenlautner added type:feature-request A new feature proposal state:needs-triage Needs to triaged to determine next steps labels Feb 14, 2024
@github-actions github-actions bot added the urgency:high Significant with a critical impact label Feb 14, 2024
@kenlautner kenlautner self-assigned this Feb 14, 2024
Copy link

This issue has been automatically marked as stale because it has not had activity in 45 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the state:stale Has not been updated in a long time label Mar 30, 2024
Copy link

github-actions bot commented Apr 7, 2024

This issue has been automatically been closed because it did not have any activity in 45 days and no follow up within 7 days after being marked stale. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 7, 2024
@kenlautner kenlautner reopened this Apr 18, 2024
@kenlautner kenlautner added the state:backlog In the backlog label Apr 18, 2024
@kenlautner kenlautner linked a pull request Sep 20, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:backlog In the backlog state:needs-triage Needs to triaged to determine next steps state:stale Has not been updated in a long time type:feature-request A new feature proposal urgency:high Significant with a critical impact
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant