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

Check and increase test coverage #366

Open

cniethammer opened this issue Dec 19, 2024 · 1 comment

Assignees

Labels

help wanted UnitTest WIP

Contributor

cniethammer commented Dec 19, 2024

While ls1-mardyn already has a bunch of unit tests, not all code parts are equally covered by them.

The test coverage should be checked and improved where needed.

cniethammer added the UnitTest label

cniethammer self-assigned this

cniethammer added help wanted WIP labels

Contributor Author

cniethammer commented Dec 19, 2024 •

edited

Loading

Code coverage reported from running unit tests with the current master (6304c0b) when running a sequential build ./MarDyn -t -d ../test_input/

Summary coverage rate:
source files: 507
lines.......: 29.3% (8393 of 28607 lines)
functions...: 35.8% (1696 of 4742 functions)

Note: The coverage tool reported a bunch of errors parsing the coverage data, which were ignored to generate the output

Here a more detailed output for the subdirectories in the codebase:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment