apache / sling-org-apache-sling-testing-emailConditional Complexity

Intro

Conditional complexity (also called cyclomatic complexity) is a term used to measure the complexity of software. The term refers to the number of possible paths through a program function. A higher value ofter means higher maintenance and testing costs (infosecinstitute.com).
Conditional complexity is calculated by counting all conditions in the program that can affect the execution path (e.g. if statement, loops, switches, and/or operators, try and catch blocks...).
Conditional complexity is measured at the unit level (methods, functions...).
Units are classified in four categories based on the measured McCabe index: 1-5 (simple units), 6-10 (medium complex units), 11-25 (complex units), 26+ (very complex units).

Conditional Complexity Overall

Legend:

51+

26-50

11-25

6-10

1-5

Alternative Visuals

Conditional Complexity per Extension

51+

26-50

11-25

6-10

1-5

Conditional Complexity per Logical Component

primary logical decomposition

51+

26-50

11-25

6-10

1-5

Most Complex Units

Top 8 most complex units

Unit	# lines	McCabe index	# params
protected void doGet() in src/main/java/org/apache/sling/testing/email/impl/EMailServlet.java	36	8	2
public List getMessages() in src/main/java/org/apache/sling/testing/email/impl/SmtpServerWrapper.java	13	3	0
public void activate() in src/main/java/org/apache/sling/testing/email/impl/SmtpServerWrapper.java	11	2	1
private int reflectiveGetEffectiveBindPort() in src/main/java/org/apache/sling/testing/email/impl/SmtpServerWrapper.java	6	1	1
public void deactivate() in src/main/java/org/apache/sling/testing/email/impl/SmtpServerWrapper.java	5	1	0
public int getEffectiveBindPort() in src/main/java/org/apache/sling/testing/email/impl/SmtpServerWrapper.java	3	1	0
public void clearMessages() in src/main/java/org/apache/sling/testing/email/impl/SmtpServerWrapper.java	5	1	0
protected void doDelete() in src/main/java/org/apache/sling/testing/email/impl/EMailServlet.java	4	1	2