Following is a quick way to identify code with low testability and hence low maintainability:
- Take any specific public method of the class
- Count for number of decision points such as following:
- Inline ifs
- If the number of decision points in a method is more than 15 or so, it could be taken as indication that it may get difficult to write unit tests covering all possible flows. Thus, the code will have lower testability.
The number of decision points in a method is also used to define/measure cyclomatic complexity of the method, or more specifically, McCabe Cyclomatic Complexity. Thus, mathematically speaking, testability can be represented as following:
Testability, T of a method is inversely proportional to No. of Decision Points, D, found in the method.
Follow him on Twitter and Google+.
Latest posts by Ajitesh Kumar (see all)
- Content Framework for Lunch & Learn Sessions on IT Applications - April 17, 2014
- APIs Performance Testing with Twitter Iago - April 17, 2014
- Mobile Apps Testing Frameworks Used at LinkedIn - April 16, 2014