-
Notifications
You must be signed in to change notification settings - Fork 15
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
Unit testing #4
Comments
Suggestions from @christopheredsall are There must be a good way to integrate with Cmake to do test discovery. Some googling required. |
Cmake test discovery does not work with either in the same way as would be expected from googletest. Instead the unit testing test executable can be run as a single ctest. The downside of this is that a single unit test failure would return a error code but ctest would report 0/1 failed. The details of the unit test output would still be logged so its not a big issue. |
We had a discussion that, due to the nature of this code, there is a lot of correctness that would be covered by integration tests (#62), and unit testing would be a little harder / less effective. That said, I can see how |
fwiw, pfunit was pretty easy to build locally (in non-MPI mode at least). |
Unit testing is absolutely required for this code. Ideally this could be done using Fortran by invoking the C API.
The text was updated successfully, but these errors were encountered: