search

OpenCDSS / cdss-app-tstool-test

Colorado's Decision Support Systems (CDSS) TSTool application functional tests
Creative Commons Attribution 4.0 International
0 stars 0 forks source link

SetDebugLevel - need a script to track down when debug is turned on but not turned off #107

Closed smalers closed 1 year ago

smalers commented 1 year ago

Sometimes I use the SetDebugLevel command in automated tests to troubleshoot an issue. Because thousands of tests are run, when debug gets turned on, it causes the log files to be larger and tests to run slower. Unfortunately, sometimes I forget to turn debug off of remove those commands from a log file and then it is hard to find which command file is the culprit, especially when a number of tests have been updated over a period of time. I need to write a script to track it down so that when it happens it is easy to fix.

I'm going to commit recent work for TSTool 14.5.1 and then write this script so that the automated tests can be streamlined.

smalers commented 1 year ago

I added the scripts/find-debug-command-files.bash script to find command files where debug was inadvertently left on. I also added a ZZ-EndChecks command file folder to run at the end of the automated tests to check processor properties to make sure debug is not set at the end of processing. Close this issue.