WHAT’S IN THIS CHAPTER?
- Identifying opportunities to use the Strategy Pattern
- Implementing the Strategy Pattern using test-driven development
- Using the Factory Pattern to select strategies at run time
WROX.COM CODE DOWNLOADS FOR THIS CHAPTER
You can find the wrox.com code downloads for this chapter at
The Strategy Pattern is used to isolate multiple algorithms, or strategies, that perform a specific task into modules that may be swapped in and out at run time. This chapter uses test-driven development to show how, through the use of strategies, algorithms may be added or removed in a way that’s independent from the client, or context, that uses them. The chapter will also describe how the Factory Pattern from Chapter 10 helps achieve this goal.
Additionally, the chapter will illustrate how programming to the interface of a strategy improves the testability, and thus reliability, of the code that consumes the strategy.
UNDERSTANDING THE PATTERN THROUGH UNIT TESTS