Seuss: Decoupling responsibilities from static methods for fine-grained configurability.

Abstract

Unit testing is often made more difficult by the heavy use of classes as namespaces and the proliferation of static methods to encapsulate configuration code. We have analyzed the use of 120 static methods from 96 projects by categorizing them according to their responsibilities. We find that most static methods support a hodgepodge of mixed responsibilities, held together only by their common need to be globally visible. Tight coupling between instances and their classes breaks encapsulation, and, together with the global visibility of static methods, complicates testing. By making dependency injection a feature of the programming language, we can get rid of static methods altogether. We employ the following semantic changes: (1) Replace every occurrence of a global with an access to an instance variable; (2) Let that instance variable be automatically injected into the object when it is instantiated. We present Seuss, a prototype that implements this change of semantics in Smalltalk. We show how Seuss eliminates the need to use class methods for non-reflective purposes, reduces the need for creational design patterns such as Abstract Factory and simplifies configuration code, particularly for unit tests. We present benchmarks showing that Seuss introduces a 34 % additional memory cost, and runs at 53 % speed, without any optimizations.

TryLinks

“…This is called Dependency Injection. Dependency injection "separates the creation of a client's dependencies from the client's behavior, which allows program designs to be loosely coupled" [9] and to "follow the dependency inversion and single responsibility principles" [8].…”

Tools and Language Elements for Testing, Encapsulation and Controlling Abstraction in Large Scale C++ Projects

“…There are several design patterns for dependency replacement like the Factory Method and Abstract Factory [45], the Service Locator [46,47] and the Depen- [48,49,50].…”

Self-generating Programs – Cascade of the Blocks

“…A dependency injection is a software design pattern used to ease dependencies in the code [9]. A basic idea is in a separation of tool users (code) from creators (factory) of the tool (object), so the creators can be easily replaced.…”