WIP: RFC Test Suite for Coding Style test
This was an experiment from some time ago to run
CodingStyleTestCase for each business templates, one by one. Here is one example test run: https://nexedi.erp5.net/test_result_module/20180320-5DB1229B
The results is that pylint reports a lot of problems and that it takes a lot of time to run the full test suite.
I took the approach of creating one independent test per business template, instead of the approach of creating a site with all business templates like we did in testNamingConventions or testHTML, but I'm not really convinced it was a good idea.
The idea behind this was that if we extend our business template checks ( for example when we translate the ERP5 Module Creation Guidelines to some scripts we can run on a business template ), we can check that each business template contain what it should contain and not just that the global result is OK.
Another reason was that this test is failing a lot and I'm not sure we can allocate time to make all business templates pass these checks.
I don't like that it runs separately from ERP5 test suite, I'm worried that developers might only check the unit test results and forget about the coding style tests.
There's also some cleanups commit we can probably merge individually.