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

Monitor test coverage #144

Open
schmoelder opened this issue Jun 19, 2024 · 1 comment · May be fixed by #206
Open

Monitor test coverage #144

schmoelder opened this issue Jun 19, 2024 · 1 comment · May be fixed by #206
Assignees
@daklauss
Milestone
v0.11.0

Comments

@schmoelder
Copy link
Contributor

schmoelder commented Jun 19, 2024 •
edited
Loading

As discussed, we want to monitor test coverage in CADET-Process. This should be reported in the CI and ideally, we only accept PRs that increase coverage.
@schmoelder schmoelder mentioned this issue Dec 3, 2024
Closed
3 tasks
@daklauss daklauss mentioned this issue Dec 3, 2024
Merged
2 tasks
@schmoelder schmoelder added this to the v0.11.0 milestone Dec 5, 2024
@schmoelder
Copy link
Contributor Author

When measuring coverage, I think it's fine to only check the CADETProcess directory. No need to check examples, docs or the tests themselves.

@daklauss daklauss linked a pull request Jan 8, 2025 that will close this issue
Open
5 tasks
@daklauss daklauss linked a pull request Jan 8, 2025 that will close this issue
Add coverage pipeline #206
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@daklauss daklauss

Labels
None yet
Projects
None yet
Milestone
v0.11.0
Development

Successfully merging a pull request may close this issue.

Add coverage pipeline fau-advanced-separations/CADET-Process
2 participants
@schmoelder @daklauss