As we saw in Chapter 6, a single Fit table may not be sufficient to define a test, and we often need to use several types of table. Usually,
ActionFixture tables have side effects on the system under test, so the underlying fixtures for the tables in a workflow test need to be organized so that they all access the same system under test.
In this chapter, we show, step by step, how fixture objects are created. We show several ways in which the fixtures underlying the tables of a single test can be coordinated.