As a developer I want to have an integration test for the full .dck file to be able to catch unintended changes to, among other things, the computation and printing of the energy balance variables.
My first thought would be to extend TestEditor (which currently only looks at storage and hydraulic .ddcks and the _mfs.dck file, but not the full .dck file to my surprise [disclaimer: I wrote the class]). There might be better ways, though, as TestEditor is getting quite big.
As a developer I want to have an integration test for the full
.dck
file to be able to catch unintended changes to, among other things, the computation and printing of the energy balance variables.My first thought would be to extend
TestEditor
(which currently only looks at storage and hydraulic.ddcks
and the_mfs.dck
file, but not the full.dck
file to my surprise [disclaimer: I wrote the class]). There might be better ways, though, asTestEditor
is getting quite big.