Laserfiche WebLink
~ ~ <br />for updating other commands in a similar .fashion (to be scoped outside of this <br />effort). If the StateMod file does not exist (e.g., because it is created <br />dynamically), the time series list will not be available to subsequent <br />commands. <br />5. Update all named-parameter commands used in CDSS to warn users about <br />unrecognized parameters. The command editors do enforce proper syntax and <br />will filter out unrecognized parameters. However, if users edit commands <br />with an editor, it is possible to introduce unrecognized parameters. In most <br />TSTooI commands, these are simply ignored without indication. Amore <br />strict approach is to warn the user when unrecognized parameter names are <br />found, so that the command can be corrected. Approximately 30 named- <br />parameter commands will be updated to include the check. <br />140.4 Implement automated regression tests for CDSS data processing. Software <br />testing involves unit testing at a low level to verify specific functionality, and <br />application testing to verify overall functionality. In addition, regression testing <br />can be performed to compare previous validated output with that of the current <br />software. The command-focused design of TSTooI typically allows developers to <br />test changes/enhancements in software without testing all features. However, <br />although software developers are developing code to specifications, they often do <br />not know all use cases for the software. Additionally, budget limitations do not <br />allow developers to test all possible combinations of input. Recent TSTooI <br />enhancements have added the compareTimeSeries O , compareFiles O , <br />and runCommands () commands. These commands can be used in automated <br />regression testing, which facilitates verifying that software output does not change <br />over time due to software or data changes. In the case of CDSS, changes in <br />HydroBase may cause changes in output, although specifying the period of record <br />for processing should minimize changes. The following activities will occur to <br />implement regression tests for TSTooI, 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. 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. TSTooI has nearly 100 commands, although not all maybe used <br />in CDSS work. Tests can be configured as being very simple but can also be <br />complex, in particular where output from one command is used as input to <br />another. For scoping purposes, it is assumed that 20 simple tests, and 10 more <br />complex tests will be included in the initial regression test configuration. <br />Once a formal standard is established, additional tests can be added as part of <br />other enhancement work, as described in other subtasks. <br />With the test plan .document, test files, and TSTooI software, RTi, DWR, and <br />CWCB staff will be able to run regression tests and verify the software at any <br />time. As appropriate, tests can be rerun to evaluate impacts of software and <br />14 <br />