Changes in results post upgrade - 8.3.14

Summary: this page lists:

  • Impacts of changes made to AIP Core 8.3.14 on Quality Model results post upgrade
  • Other impacts of changes made in AIP Core 8.3.14

All changes in results related to extensions are now listed in the extension documentation and will not appear in this page.

Impacts of changes made in AIP Core 8.3.14 on Quality Model results post upgrade

Metrics Assistant

AIPCORE-136 - Avoid Artifacts with high Commented-out Code Lines/Code Lines ratio - 7126

A correction has been made to improve the way in which the Metrics Assistant handles input files for the metric "Avoid Artifacts with high Commented-out Code Lines/Code Lines ratio - 7126".  In previous releases where multiple execution units existed for a single technology, the analysis order of input files used to produce the results for "Avoid Artifacts with high Commented-out Code Lines/Code Lines ratio - 7126" was liable to vary, therefore producing different results in successive snapshots. This behaviour has been changed and therefore after an upgrade to AIP Core 8.3.14:

  • A post upgrade consistency snapshot will produce different results to snapshots generated in previous releases of AIP Core due to the analysis order of input files being fixed.
  • Subsequent snapshots in AIP Core ≥ 8.3.14 will always use the same analysis order for input files, therefore producing consistent results.

.NET

AIPCORE-298 - Avoid using untyped DataSet - 7460

The rule Avoid using untyped DataSet - 7460 (which is delivered as part of AIP, rather than the .NET Analyzer extension) has been set as deactivated and detached by default. Therefore after an upgrade to AIP Core 8.3.14 and the generation of a post-upgrade consistency snapshot, results may differ: the rule will no longer be triggered during an analysis.

Avoid NoSQL injection on MongoDB (C#) - 8418 and Avoid second order SQL injection - 8420

The rules Avoid NoSQL injection on MongoDB (C#) - 8418 and Avoid second order SQL injection - 8420  (which are delivered as part of AIP, rather than the .NET Analyzer extension) are now set as "critical" by default. Therefore after an upgrade to AIP Core 8.3.14 and the generation of a post-upgrade consistency snapshot, results may differ: there may be an increase in critical violations and a corresponding decrease in non-critical violations.

Other impacts of changes made in AIP Core 8.3.14

N/A