...
| Info | ||
|---|---|---|
| ||
Note: eWater has a suite of over 600 regression test projects that are used to check for changes introduced in Source during software development. This regression test suite is run on almost every change made to the software code, allowing any code changes that cause regression test failures to be readily identified. If a test project has trouble running or the results are not asexpected, then the regression test has failed. eWater’s software developers' team and hydrologists decideif the change in results is as intended or not. Each Beta and Production software release includes a list of known changes to these regression tests. To view the regression test changes and a report about the regression test suite for a specific release, see Source Revision History. |
Source users can also create and run local regression tests. Establishing local regression tests is good practice as it allows users to identify potential result changes when upgrading models to newer versions of Source. In some circumstances, these local tests can be included in the eWater Regression Test Suite, please contact eWater if interested.
...
Scenario and analysis list: this box will display all the available scenarios combined with all possible run configuration analysis types in your Source project file (information on run configuration analysis types can be found at Configuring Scenarios. <span>Configuring Scenarios</span>). Only run scenario and analysis type (e.g., Manual Calibration - Flow Calibration analysis) is enabled for the selection. The user needs to select the applicable Scenario (such as Automatic Calibration) and applicable analysis type (such as Single Analysis), Multiple scenario and run analysis type combinations can be selected. Scenario and run analysis type combinations which are not relevant for a project (such as Run with warm up which is not applicable for the catchment model in this example) will not be available.
All selected recorders for all the run scenarios and analysis types in a Source project file (e.g., Manual CalibrationCalibration -Flow Flow Calibration analysis) in a Source project file will be outputted/written to the regression test sub-folder during the Test Builder, but only selected items (such as Automatic Calibration - Single Analysis in Figure 1) will will be checked during the Test Runner. Therefore, to keep regression test file size and run time to a minimum the user should preferably create very specific Source projects for regression testing – including only the scenarios and recorders required for testing.
...
If your regression test fails, read the error message(s) and look at the release notes and regression test changes for releases between the version of Source in which you created your test project, and the one in which you ran your regression test. You can also run the regression test in some of these intermediate releases (beta) to determine in which version the errors start. If you still cannot resolve the issue or do not have access to the beta releases, please contact Source support.
...