The focus of this chapter has been testing our Flux architectures. There are two types of tests that we employ to do this: functional and performance. With functional units, we verify that the units of code that make up our Flux architecture are behaving as expected. With performance units, we're validating that the code is performing at the expected levels.
We introduced the Jest testing framework to implement unit tests for our action creators and our stores. We then discussed the various tools in the browser that can help us troubleshoot performance issues at a high-level. These are the types of things that impact the user experience in a tangible way.
We closed the chapter with a look at benchmarking our code. This is something that takes place at a low-level and is most likely related to the state transformation functionality of our stores. Now it's time to consider the implications a Flux architecture has on the overall software development lifecycle.