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

[CI] Signal test coverage changes (SimpleCov + Undercover gems) #13102

Open
filipefurtad0 opened this issue Jan 28, 2025 · 0 comments · May be fixed by #13101
Open

[CI] Signal test coverage changes (SimpleCov + Undercover gems) #13102

filipefurtad0 opened this issue Jan 28, 2025 · 0 comments · May be fixed by #13101
Assignees

Comments

@filipefurtad0
Copy link
Contributor

What we should change and why (this is tech debt)

We should improve usage of simplecov report by signalling devs whether code changes are having a (negative) impact on code coverage. The undercover gem should be able to provide this information, when integrated in the CI, as it needs a build run on new branches so it can be compared with master branch.

Context

This came up before and on last week on delivery circle meeting.

Impact and timeline

Making better use of the simplecov gem data output. A related discussion can be found here.
.

@github-project-automation github-project-automation bot moved this to All the things 💤 in OFN Delivery board Jan 28, 2025
@filipefurtad0 filipefurtad0 linked a pull request Jan 28, 2025 that will close this issue
4 tasks
@sigmundpetersen sigmundpetersen moved this from All the things 💤 to In Progress ⚙ in OFN Delivery board Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress ⚙
Development

Successfully merging a pull request may close this issue.

1 participant