Automocking is a time-saving feature of StructureMap that allows you to easily instantiate the Class Under Test by automatically resolving the constructor dependencies of the class with Mocked out instances.
From Evolutionary Developer:
Automocking is a time-saving feature of StructureMap that allows you to easily instantiate the Class Under Test (the class that will be used in the GIVEN statement of the Scenario) by automatically resolving the constructor dependencies of the class with Mocked out instances. Test classes therefore become decoupled from the constructor(s) of the Class Under Test. Meaning that you'll get a test that fails if you change a constructor instead of a test that won't build. This is a debatable point but can be considered an advantage in TDD - you get feedback from your tests as opposed to the compiler, as it should be.
Some usage examples can be found here.
