ESCOMP / ESCOMP/CTSM

Re-implement build-namelist unit tester for CLM

Open
#92 0 comments 0 reactions 1 assignee Claimed by @ekluzek View on GitHub
enhancement priority: low
Dominant language
Fortran
Stars
352
Forks
361
Avg merge
2d 21h
Merged PRs (30d)
7

Description

**Erik Kluzek < erik > - 2013-04-08 16:27:28 -0600**
**Bugzilla Id:** [1652](http://bugz.cgd.ucar.edu/show_bug.cgi?id=1652)
**Bugzilla CC:** bugzillaMuszala, mvertens, rfisher, sacks,

The unit tester for CLM is quite awkward, bulky, and hard to maintain. The principle of having a unit test is a good one though, so I'd like to see us continue to have one. But, it would be good to throw this version away and re-implement it completely. I've thought this for a long time, but it isn't something we can spend time on.

I think a better way to implement it would be for it to have test lists similar to our other successful test frameworks. Then a file (probably XML) that lists the master list of tests, and the expected results. So it could specify if it was an expected fail condition or not. It should also probably understand and be able to set all the different options to the build-namelist.

I think something could be setup to read the XML file, that would be pretty lightweight. So the main effort would be in the XML file itself.

I don't know when we might be able to spend time on this, but I'll have a bug report so we don't forget about it.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.