The trend for modified code shows a negative percentage though application trend is supposed to show the effect of the added and modified code on the health factors.
The example screen shot above shows the negative percentage of -42.3% in the modified tab.
Details
This is not unusual as the negative value is a comparison of values of this version with the values in the last iteration (ie two sprints/iterations/scans etc). This could be because of deleted code which is not reported or bad code that was removed.
-
To ensure that there is no issue in calculation, make sure that the file path is not changed. Trend calculation is based on CRC ie Cyclic Redundancy Check and file paths. So when scanning code with the Local Agent or CLI , ensure that the folder structure remains the same across versions, as it is used to cipher scanned files. Please refer How to use Delta Analysis in Agile-driven code bases
- The impact on the overall software health score because of the -ve score in software health depends on the total LOC of the application. For eg if the subset of modified code is small (for example 1k modified LOC as compared to 100K total LOC), even though it dropped, when looking at 1K modified, the overall impact in a larger 100K application is negligible. Same concept is applicable for software resiliency, agility and elegance
Ticket
37708
Related Articles
How to estimate size and health of high frequency code iterations using the delta analysis feature
Additional Resources
CAST Highlight Troubleshooting Guides
CAST Highlight Product Documentation
Comments