Devs,
Unit test capability was added to v3.0 through patch update v3.0.1. You can see these when you ‘git checkout v3.0.1’. Look toward the bottom of
https://bitbucket.org/pflotran/pflotran/commits/tag/v3.0.1?page=2
For example:
https://bitbucket.org/pflotran/pflotran/commits/2aa5cb115afbc10e30d35630e748bf5329e95309
https://bitbucket.org/pflotran/pflotran/commits/28cfb4f75f4822cae704763a176d74e1313ff6ed
etc.
These were never added to back master.
The implementation in v3.0.1 revolves around embedding testing within the process or constitutive relation. I highly recommend implementing unit tests in a different manner. We create new unit test process model(s) (e.g., pm_unittest_eos.F90 -> pm_unittest.F90 -> pm_base.F90) and that runs all the testing. When the tests are embedded in the actual process model or constitutive relation, the flags, storage, etc. can be invasive and messy. The pm_unittest framework would handle all the I/O and execution.
Glenn