李小璐与贾乃亮滚床单:计算机英语

On the flip side, container simulation—Mock Object based tests require that your action code is not tightly coupled
with the underlying J2EE container. This requires a cleaner design and cleaner delineation between your
model and the container. Typically, you can get a fairly clean design by using an Abstract Factory from your
Actions. Thus, your Actions never directly deal with J2EE; they talk to the Abstract Factory to get model objects.
The Abstract Factory may in turn talk to the J2EE services, like JNDI, to look up and interact with EJBs. Then,
for testing, you create an Abstract Factory that delivers Mock Objects for testing. This is the approach I usebecause
the advantage of using container simulation is you don’t have to deploy your code to the container to test it.
In short, the reason to use container simulation is speed. Tests that take a long time to run don’t get run as often.
TDD favors fast running tests.