A great way to improve the testability of your software is to add logging! A log with all errors, warnings, faults, exceptions, dialog messages, or whatever is interesting for you in one file!
For most programmers it is relative easily to build in logging. When an application has a single class/procedure/library to handle errors, it is easy to build in logging. Depending on what you log it could become very easy for programmers to find the causes of crashes/bugs. If you are able log all user actions, it is just a matter of walking through the log file for the reproduction steps. Additionally, not all problems are visible in the GUI, sometimes a problem is only reported in a log file or some strange output is written to the log file.
However, when you have several servers up and running (database, application server, web server) it could produce a lot of logging. Testers are also humans.. so it could happen that you miss an important message in the log….
|audio_logwatch.bat||An example file to start multiple instances of logwatcher.exe to watch files.|
|error.wav||Sample wav file, that gives you the raspy voice of James Bach during a bout of bronchitis.|
|license.txt||The program is released under the GPL 2.0 license.|
|logwatcher.au3||The source code of the program.|
|logwatcher.exe||A compiled version of the script, ready to be used.|
|readme.txt||A file with some information about the tool and credits to James Bach.|
|watchlist.txt||The file that contains the patterns to look for in the log files.|