You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basic CMakeLists.txt for configuration and particularly interfacing with pFUnit.
A couple of placeholder unit tests to "test the testing".
Build and cache pFUnit in the GH actions workflow, build the test executable and run the tests.
Currently (17.02.2022) some tests are implemented in the hack_doconcurrent branch using CTest and pFUnit, so I'm assuming some of you know about this testing framework. pFUnit looks like a popular option for fortran. It's maybe not as well documented and feature-rich as frameworks in other languages, but seems to be used by many projects out there. Alternatives are Funit, FRUIT and Ftunit but pFUnit is the only one that ibviusly looks actively maintained?
I've played around with it, it's straightforward to install and use. At least following basic examples available at
A separate list of command line options is defined for both xcompact3d
and the decomp2d library. Because they are currently the same, the
list could technically be defined one for decomp2d with the PUBLIC
attribute. However, it is likely that these 2 lists will diverge in
the future. Or at least it's helpful to allow it.
A minimum setup could be
CMakeLists.txt
for configuration and particularly interfacing with pFUnit.Currently (17.02.2022) some tests are implemented in the
hack_doconcurrent
branch using CTest and pFUnit, so I'm assuming some of you know about this testing framework. pFUnit looks like a popular option for fortran. It's maybe not as well documented and feature-rich as frameworks in other languages, but seems to be used by many projects out there. Alternatives are Funit, FRUIT and Ftunit but pFUnit is the only one that ibviusly looks actively maintained?I've played around with it, it's straightforward to install and use. At least following basic examples available at
https://github.com/Goddard-Fortran-Ecosystem/pFUnit_demos
It also had support for MPI. I don't know if this is common among fortran frameworks, but it sounds relevant to me.
Tests are written in free form fortran, e.g.
that is meant to be parsed and compiled. But a CMake module is provided that takes care of everything, so that
should be enough to generate test executable
my_tests
. See Using pFUnit.The text was updated successfully, but these errors were encountered: