We want the architecture of our application to be the best that it can possibly be. It may sound silly to have to state this, but it does bear repeating from time to time, as a reminder that the work we're doing with Flux has the potential to make or break the success of the application. The best tools we have in our arsenal are unit tests and performance tests. These two activities are equally important. Being functionally-correct but slow as hell is a failure. Being fast as hell and riddled with bugs is a failure.
A huge contributing factor to implementing successful tests is to focus on what's relevant. We'll spend time in this chapter thinking about what the important tests are for Flux architectures—from both a functional and a performance perspective. This is especially important to think about given how new Flux is to the community. We'll focus on specific Flux components and design some unit tests for them. We'll then think about the difference...