Retire the tools/tests framework for CESM test system custom tests that do the same thing #2279
Closed
7 tasks done
Labels
code health
improving internal code structure to make easier to maintain (sustainability)
The test/tools framework should be retired for use of the CESM test system custom tests that tests tools.
Right now this framework only tests a few tools, with a few others that will be retired shortly. Testing for python scripts is now better handled with our python testing framework. The one thing the python testing framework can't do is to make sure the top level skeleton tools work in terms of paths. The tools/testing framework also made it easy to setup tools that weren't under the python framework, or older FORTRAN based tools, or tools based on perl, or NCL or another language.
Some reasons to shift:
It's from a few generations ago of a test framework for CAM
We did realize that having a test tool that tests the top level scripts is useful though, if the paths for the top level tool become screwed up. Since, that's almost the ONLY thing that can go wrong in the top level skeleton script any problems are going to be easy to solve. But, since the top level scripts are what users interact with in the end it's the thing we want to ensure is working for people.
This is something we agreed to at our last CTSM software meeting.
Definition of Done:
The text was updated successfully, but these errors were encountered: