Hi OTRS-Developers, Fred is a development module whose purpose is to find problems in any OTRS module as they occur (as opposed to reading about them in the Apache logfile). Fred traces the execution of OTRS modules and scrutinizes their output in order to find any problems (for instance with regards no HTML-tags not being closed, etc.). Judging from our own experience, Fred is a very valuable tool as it makes problems visible very early in the development cycle. If Fred detects an error it includes the error warning in the HTML-Output of OTRS just in time. Actually it finds * perl warnings (for example uninitialized value) * html syntax errors * translation missing Now we would like to include more useful functions. So please give feedback if you have any ideas yourself. At the moment we discuss the following features: * improve the handling of the 'translation missing' detection * a function to detect {ConfigObject}->Get calls without a feedback * otherwise a detection to find unused config xml settings * function to include benchmarking and profiling modules like Benchmark, Devel::DProf and Devel::SmallProf Thank you for your new ideas. Suggestions for improvements to the existing functionality is also very welcome. ((enjoy)) Thomas Further information * actually Fred is only available as cvs checkout * also see cvs.otrs.org * you also need the otrs-link module and some cpan modules * the settings required by Fred can be done in sysconfig