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

reach 80% coverage #179

Open
12rambau opened this issue Jan 29, 2024 · 0 comments
Open

reach 80% coverage #179

12rambau opened this issue Jan 29, 2024 · 0 comments
Labels
impact: high Something that is relevant to nearly all users kind: maintenance Improving maintainability and reducing technical debt tag: CI Pull requests that update GitHub Actions code

Comments

@12rambau
Copy link
Member

Now everything is correctly set up for the coverage report ad that's a good way to monitor the refactoring effort.
I want to reach 80% coverage before moving forward with a definitive release of v1.

As no methods were tested in the previous implementation, it gives an excellent idea of what has been refactored and what hasn't.
@12rambau 12rambau added kind: maintenance Improving maintainability and reducing technical debt tag: CI Pull requests that update GitHub Actions code impact: block-release Should block a release from happening. Only use if this is a critical problem we don't want to ship impact: high Something that is relevant to nearly all users and removed impact: block-release Should block a release from happening. Only use if this is a critical problem we don't want to ship labels Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
impact: high Something that is relevant to nearly all users kind: maintenance Improving maintainability and reducing technical debt tag: CI Pull requests that update GitHub Actions code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@12rambau