Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Table of Contents

Files, programs, methods, etc. with a high complexity are hard to change:

  • It takes time for developers to understand them.
  • Changes can lead to regressions if there is no automated unit tests on the modified resources.

Analyzing Complexity

Complexity Widget

Add the Complexity widget to your dashboard:

And have a look at the distribution to check if you do not have too many very complex methods or files.

You can then drill down.

Metric hotspot Widget

Add the Metric hotspot widget to your dashboard with metrics like complexity /file, complexity /method, etc to hunt for high-complexity components.

  • No labels