This page should describe Verification and Unit Tests performed for this stand alone feature and should provide links to all the result pages.
| Table of Contents |
|---|
Summary
Short summary of what was done and what was the resultUnit, integration, and simulation tests were developed in standalone HOMME.
Unit Testing
Unit Testing: short-desciption-of-testing-here
Date last modified:
Contributors:(add your name to this list if it does not appear)
Provenance: (Run provenance Link, Code Tag, etc:)
Results: (link to results, data and plots)
How was XXX be tested? i.e. how do we know when we have met requirement XXX. Will these unit tests be included in the ongoing going forward?
Verification Test 1
Verification Test 1: short-desciption-of-testing-here
Date last modified:
Contributors: (add your name to this list if it does not appear)
Provenance: (Run provenance Link, Code Tag, etc.)
Results: (link to results, data and plots)
...
Element-local unit tests check for mass conservation, area conservation, extrema nonviolation, and reversibility of maps when expected. A driver can be called from standalone HOMME or E3SM. A string, "ERROR," is output and so can be grepped for in a testing script if a unit test does not pass. We don't quite have a unit-testing framework yet for E3SM, but when we do, this can be included in it.
Verification Test 1
A second set of tests checks correctness at the level of API calls. Again, a greppable string is output on failure. l2 error output from a sequence of runs of this test provide order of accuracy checking. The following figure is an example of what can be produced and is described in the latex design document.