Tests to assure debug remnants are not in our sources?

Subject: Tests to assure debug remnants are not in our sources?

From: Erik Huelsmann <..hidden..>

Date: Fri, 11 Sep 2015 23:05:48 +0200

Hi,

Every once in a while, some debug code ends up in a release.

Based on the code that I used to tighten the checks on modules loading correctly, I could quite quickly implement checks to ban certain code sequences. My current idea is to blacklist the following snippets:

"use Carp::Always"

"use Data::Dumper"

"print STDERR"

not to appear in any files in LedgerSMB/, bin/ and LedgerSMB.pm

Any objections?

Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.

Robust and Flexible. No vendor lock-in.

------------------------------------------------------------------------------