...
This is only an example of my point in this post:
...
Kiuwan scans the code searching for broadly accepted “bad smells”. But, depending on specific circumstances, those defects could not be such.
What to do in those cases?
Below I will go through the most common situations reported by our customers. For each of them, I will provide some action you can do.
...
Please, visit https://www.kiuwan.com/docs/display/K5/FAQs+-+Frequently+Asked+Questions#FAQs-FrequentlyAskedQuestions-HowcanIdeactivatearule for help on how to do it.
Case 2: “The rule is generally applicable, but this defect is not really a defect” : Mute that defect and report it to us
...
In case you are muting a defect because you consider that “is not a defect” and the rule is not properly working (i.e. a false positive), please do not hesitate to contact us to report the issue. We will do our best to fix it as soon as possible.
Case 3:
...
Case 3: “Some files should not be analyzed and defects found in those files should be not be raised” : Exclude those files from the analysis
A very common scenario is when you are analyzing your code but you are obtaining defects in files that you cannot fix for whatever reason. Common reasons are because those files are “open source” , “generated code” or “third-party code”. You cannot modify them, but their defects are decreasing the indicators of your application.
...
You can visit https://www.kiuwan.com/docs/display/K5/Analysis+Management and https://www.kiuwan.com/docs/display/K5/Code+analysis+using+the+downloaded+agent#Codeanalysisusingthedownloadedagent-Fromgraphicalinterface to see how to do it (in the cloud or locally, respectively).
Case
...
4: “Some rules would need to be adapted to my circumstance to properly work” : Customize their behavior
...
Most of Kiuwan rules’ behavior can be customized. Kiuwan rules come with “default” parameters, i.e. they work using “factory settings”.
...