Laserfiche WebLink
<br />this menu displays all related read commands. In StateDMI, the top level <br />menu will contain entries like "Commands...Climate Stations". Selecting this <br />menu will display all commands related to climate stations. For clarity and to <br />explain the order of menus, it maybe necessary to prefix each menu with a <br />data component group (e.g., "Commands...Climate Station Data -Climate <br />Stations"). This will result in longer top-level menus but will not impact <br />functionality or increase the number of menus. <br />3. Add redundant menus where a file is used in both StateCU and StateMod. In <br />cases where files are shared between StateCU and StateDMI, the current <br />standard is to include commands with the model that is "closest" to the <br />creation of the files, while referring the user to the other model in the other <br />case. For example, StateMod diversion rights commands are listed with the <br />StateMod menus. When StateCU is selected, the menu displays a message <br />dialog telling the user to use the StateMod diversion right commands. This <br />requires that the user switch from StateCU to StateMod mode. Given that <br />time series processing is being phased out of StateDMI and into TSTool, <br />redundant menus will be kept to a minimum (diversion rights commands will <br />be included in StateCU, and imgation practice commands will be included in <br />StateMod). <br />141.8 Implement automated regression tests for CDSS data processing. See the <br />TSTool 140.4 discussion for background. The following activities will occur to <br />implement regression tests for StateDMI, to help developers, maintainers, and key <br />system users verify software functionality and results: <br />1. Write a test plan document with emphasis on regression testing. This <br />document will describe the location and organization of test files, and how to <br />run the regression tests. <br />2. Implement compareFiles () and runCommands () commands in <br />StateDMI, similar to TSTool, to support automated regression testing. <br />3. Develop test input data, and commands files, which can be re-run at any time <br />to verify the software functionality, and save validated output to be used for <br />comparison. StateDMI has approximately 220 commands, although not all <br />can be tested individually. Tests can be configured as being very simple (e.g., <br />set data for one station and write output) and can also be complex, in <br />particular where output from one command is used as input to another. For <br />scoping purposes, it is assumed that the production StateCU and StateMod <br />model files for one basin (e.g., Rio Grande, as supplied by the State} will <br />serve as the baseline. Commands files will then be configured to compare the <br />baseline with current output. <br />4. Additionally, 10 simple commands files will be configured to test general <br />capabilities and serve as a starting point to add other tests as development <br />occurs. Once a formal standard is established, additional tests can be added as <br />part of other enhancement work, as described in other subtasks. <br />24 <br />