Comment 2 for bug 1388228

> Any particular reason you are using run_tests.py instead?

They do different things. :)

The code check consists of multiple rules files. These contain a regex and a set of allowed examples and and another list of forbidden examples.
run_tests.py goes through all the rules and verifies the allowed examples don't raise any warnings and that forbidden examples trigger the rule as expected. This is done to ensure that the rules behave the way we want and catch issues. (As a bonus, it makes it really easy to use Test Driven Design to write new rules or expand existing ones before running it on the WL source)

CodeCheck on the other hand, check the Widelands source code using the specified rules.

So the failures above indicate that the check for camel_case_for_classes above indicates that the rule doesn't catch the unwanted examples which means it won't be able to find and warn about it in the WL code base.